Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d5803e7d5246f522a415865c37cdd898e3a8442701f064b913208626a9b5633

Tx prefix hash: 38c8eceeef0b092dc2068c93527aa23d5819475ed1719b13ca0fca4e19ed8e6a
Tx public key: 1837e393fbd9c8f8bfcb392ba24464047fab13e4bd29cec254bbf4079c45af69
Timestamp: 1699364013 Timestamp [UCT]: 2023-11-07 13:33:33 Age [y:d:h:m:s]: 01:148:09:48:32
Block: 886477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367252 RingCT/type: yes/0
Extra: 011837e393fbd9c8f8bfcb392ba24464047fab13e4bd29cec254bbf4079c45af690211000000014b8f5122000000000000000000

1 output(s) for total of 0.709142817000 dcy

stealth address amount amount idx
00: cc4791eb013155e59317387d43aef7f65b2985a8334dd671e91daf1667d0b4e9 0.709142817000 1342304 of 0

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": 886487, "vin": [ { "gen": { "height": 886477 } } ], "vout": [ { "amount": 709142817, "target": { "key": "cc4791eb013155e59317387d43aef7f65b2985a8334dd671e91daf1667d0b4e9" } } ], "extra": [ 1, 24, 55, 227, 147, 251, 217, 200, 248, 191, 203, 57, 43, 162, 68, 100, 4, 127, 171, 19, 228, 189, 41, 206, 194, 84, 187, 244, 7, 156, 69, 175, 105, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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