Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c56b7f34de45b59bd47eba3d1f010bcc963cbede6e8ed4bef1fe14c22e8d02f

Tx prefix hash: 53bac9f742bedace1e2fd7bee23faca75d13c129f87faf51057c92ec8de029db
Tx public key: ed1df125868e25a3f78c013c6241d6ea53eeadf67682e6a68587edc189f38680
Timestamp: 1711342002 Timestamp [UCT]: 2024-03-25 04:46:42 Age [y:d:h:m:s]: 01:234:06:03:05
Block: 985798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426099 RingCT/type: yes/0
Extra: 01ed1df125868e25a3f78c013c6241d6ea53eeadf67682e6a68587edc189f3868002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9673d663256675ee1b6d8e4f5a9f314f2463aa935e16e94f28b6dcfddff8efb9 0.600000000000 1446017 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": 985808, "vin": [ { "gen": { "height": 985798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9673d663256675ee1b6d8e4f5a9f314f2463aa935e16e94f28b6dcfddff8efb9" } } ], "extra": [ 1, 237, 29, 241, 37, 134, 142, 37, 163, 247, 140, 1, 60, 98, 65, 214, 234, 83, 238, 173, 246, 118, 130, 230, 166, 133, 135, 237, 193, 137, 243, 134, 128, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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