Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4f2ba81b2d5851069e88cc8a441f865bd877a4859a7eccbdb17795a40cb6c10

Tx prefix hash: 6bb5650b517716d9c3f2fdb3d3c82937a7210728d52559b591f4c1f4bb1be9a2
Tx public key: 4732f9d1f1026a1ac2f2b52a8060ad25d06952205e0f774567a23c9ca168b5ce
Timestamp: 1764734446 Timestamp [UCT]: 2025-12-03 04:00:46 Age [y:d:h:m:s]: 00:001:11:05:40
Block: 1425294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1067 RingCT/type: yes/0
Extra: 014732f9d1f1026a1ac2f2b52a8060ad25d06952205e0f774567a23c9ca168b5ce02110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83cfc4d2cdd716116ea5bdcd5109e3e878278387b8a4c87fde7020add9b97ddb 0.600000000000 1913927 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": 1425304, "vin": [ { "gen": { "height": 1425294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83cfc4d2cdd716116ea5bdcd5109e3e878278387b8a4c87fde7020add9b97ddb" } } ], "extra": [ 1, 71, 50, 249, 209, 241, 2, 106, 26, 194, 242, 181, 42, 128, 96, 173, 37, 208, 105, 82, 32, 94, 15, 119, 69, 103, 162, 60, 156, 161, 104, 181, 206, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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