Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d93b811d5be506a21e194602d230502f8c7c7127473bfb3e6a9df4dcba96230

Tx prefix hash: 2dd4f2ea116b764597b9345327c0b2b1d028ab93eaaaf47e2e51505e24880900
Tx public key: 719cbfe353c0138cbde86a5f1945e801d933d836443c571c32d636f92a946373
Timestamp: 1759692191 Timestamp [UCT]: 2025-10-05 19:23:11 Age [y:d:h:m:s]: 00:039:14:11:13
Block: 1383504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28357 RingCT/type: yes/0
Extra: 01719cbfe353c0138cbde86a5f1945e801d933d836443c571c32d636f92a946373021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c446de865e7a7e9a8b8a4dcd806a58e29e12a4fe906d51eb842d4d9361f7d7b0 0.600000000000 1871651 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": 1383514, "vin": [ { "gen": { "height": 1383504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c446de865e7a7e9a8b8a4dcd806a58e29e12a4fe906d51eb842d4d9361f7d7b0" } } ], "extra": [ 1, 113, 156, 191, 227, 83, 192, 19, 140, 189, 232, 106, 95, 25, 69, 232, 1, 217, 51, 216, 54, 68, 60, 87, 28, 50, 214, 54, 249, 42, 148, 99, 115, 2, 17, 0, 0, 0, 4, 223, 195, 186, 73, 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