Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8aa1b6fefdc9332f46b3e61175ff281cd52241c351571f78f789f0492aef1b2f

Tx prefix hash: 85664829c75151579033916ad4a1434b516127533f145c4bfd1601dde535f3e2
Tx public key: 7405cbc11c13846754a8ba1216d3f1ed39cd0ea1d8bfc076793ec964f8f142a7
Timestamp: 1758969138 Timestamp [UTC]: 2025-09-27 10:32:18 Age [y:d:h:m:s]: 01:055:18:45:54
Block: 1377509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305985 RingCT/type: yes/0
Extra: 017405cbc11c13846754a8ba1216d3f1ed39cd0ea1d8bfc076793ec964f8f142a702110000000497baf922000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a5408114be6ca9a8ac30f4ac58200505b8c3723fa3c37998118d377e3aaf2c5e 0.000600000000 1865604 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": 1377519, "vin": [ { "gen": { "height": 1377509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5408114be6ca9a8ac30f4ac58200505b8c3723fa3c37998118d377e3aaf2c5e" } } ], "extra": [ 1, 116, 5, 203, 193, 28, 19, 132, 103, 84, 168, 186, 18, 22, 211, 241, 237, 57, 205, 14, 161, 216, 191, 192, 118, 121, 62, 201, 100, 248, 241, 66, 167, 2, 17, 0, 0, 0, 4, 151, 186, 249, 34, 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) | monero version: