Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3733f45c61e9f15cb7028e8ce91beabe8fbcd9e52471901b9f163ccd59bc0e2f

Tx prefix hash: bf00bbc823ed8d1d7585cc0378845a10b82c46fd1d453a508b3f2d357b320e48
Tx public key: cd51bb3ca302ec26d7071e8509f6ba95362c4cb40a1c78ddd101c4e34098dc2f
Timestamp: 1696910171 Timestamp [UCT]: 2023-10-10 03:56:11 Age [y:d:h:m:s]: 01:186:08:37:03
Block: 866335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394231 RingCT/type: yes/0
Extra: 01cd51bb3ca302ec26d7071e8509f6ba95362c4cb40a1c78ddd101c4e34098dc2f02110000000975e3f0e9000000000000000000

1 output(s) for total of 0.826937230000 dcy

stealth address amount amount idx
00: a957205e05ceccc2625d5e6ba9ff140f9e9027791d1640afc37a77598ed628d5 0.826937230000 1320915 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": 866345, "vin": [ { "gen": { "height": 866335 } } ], "vout": [ { "amount": 826937230, "target": { "key": "a957205e05ceccc2625d5e6ba9ff140f9e9027791d1640afc37a77598ed628d5" } } ], "extra": [ 1, 205, 81, 187, 60, 163, 2, 236, 38, 215, 7, 30, 133, 9, 246, 186, 149, 54, 44, 76, 180, 10, 28, 120, 221, 209, 1, 196, 227, 64, 152, 220, 47, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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