Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a3ca3a1bbc161c8d3748d3cbb30acb10b99eca36675f80af3a9f3c3c120f426

Tx prefix hash: 36c3ea32d19d31a2fdafd86dfcf7a25b91b875a752a215e76c598c7a0b63c3e1
Tx public key: e33622372ce3ae738e37fb1d8b17ac8ee7c6c44efd80ae8aff620ad2f80e3c4e
Timestamp: 1751304096 Timestamp [UCT]: 2025-06-30 17:21:36 Age [y:d:h:m:s]: 00:180:21:15:41
Block: 1315984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127531 RingCT/type: yes/0
Extra: 01e33622372ce3ae738e37fb1d8b17ac8ee7c6c44efd80ae8aff620ad2f80e3c4e02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e0d797fa90d315988bc47aabf1aecc5f944f438235042832987e8fdcb5723f4 0.600000000000 1803641 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 dinasty-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": 1315994, "vin": [ { "gen": { "height": 1315984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e0d797fa90d315988bc47aabf1aecc5f944f438235042832987e8fdcb5723f4" } } ], "extra": [ 1, 227, 54, 34, 55, 44, 227, 174, 115, 142, 55, 251, 29, 139, 23, 172, 142, 231, 198, 196, 78, 253, 128, 174, 138, 255, 98, 10, 210, 248, 14, 60, 78, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8