Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 073641e7eb983f917681dd96ae4fc0159cfc2c7c9605b9f24b1cd0ce0a0d4e8b

Tx prefix hash: 8a044b91fadf25677c6c3bdad0b9565cbc749e7d5d4811a5acf23f8c4cdc601f
Tx public key: 564915df07e9800b16af1207c3fb374317e1e49445875012a70e90151d21b38c
Timestamp: 1746219857 Timestamp [UTC]: 2025-05-02 21:04:17 Age [y:d:h:m:s]: 00:314:19:18:05
Block: 1274405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222648 RingCT/type: yes/0
Extra: 01564915df07e9800b16af1207c3fb374317e1e49445875012a70e90151d21b38c02110000000201491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 96a17082caf5c3cc9ac5ddae0097e23cfa19a4e8867a0d8fdc2d5a70260319e1 0.000600000000 1761700 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1274415, "vin": [ { "gen": { "height": 1274405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96a17082caf5c3cc9ac5ddae0097e23cfa19a4e8867a0d8fdc2d5a70260319e1" } } ], "extra": [ 1, 86, 73, 21, 223, 7, 233, 128, 11, 22, 175, 18, 7, 195, 251, 55, 67, 23, 225, 228, 148, 69, 135, 80, 18, 167, 14, 144, 21, 29, 33, 179, 140, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369