Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc9da96c68f34c8a5f7b154d26107f98ae93e2205f10041026ddd1fa6f64fb6c

Tx prefix hash: 15eca56556cd0c33ce364ca163b672a57757ab5afd8c1d30726a58356862f8bd
Tx public key: a04227b029fa250f71376cb0291bd18ee4629a0852b3a7aa2cc773c2c9d1b88c
Timestamp: 1720590453 Timestamp [UCT]: 2024-07-10 05:47:33 Age [y:d:h:m:s]: 00:276:14:51:28
Block: 1062456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197632 RingCT/type: yes/0
Extra: 01a04227b029fa250f71376cb0291bd18ee4629a0852b3a7aa2cc773c2c9d1b88c02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a25b034e170eec105df0d7dd63ef45ab0383bb106b28b26974ff1991435fca15 0.600000000000 1532959 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": 1062466, "vin": [ { "gen": { "height": 1062456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a25b034e170eec105df0d7dd63ef45ab0383bb106b28b26974ff1991435fca15" } } ], "extra": [ 1, 160, 66, 39, 176, 41, 250, 37, 15, 113, 55, 108, 176, 41, 27, 209, 142, 228, 98, 154, 8, 82, 179, 167, 170, 44, 199, 115, 194, 201, 209, 184, 140, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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