Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6a7e74c930f06e3c831b13818b47e166bb05dcf49eee1c2704548d6ffd92863

Tx prefix hash: 3a956b4d960ea9cc6b728c1ebaf1829a1cf0b2564623faf2a37e64630f927a43
Tx public key: 53cf6323bbe4db1d4b8e4c12a22a1c262c748ef55d8b55a3c7a18a299e1aaec0
Timestamp: 1708901059 Timestamp [UCT]: 2024-02-25 22:44:19 Age [y:d:h:m:s]: 01:257:00:45:48
Block: 965550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442421 RingCT/type: yes/0
Extra: 0153cf6323bbe4db1d4b8e4c12a22a1c262c748ef55d8b55a3c7a18a299e1aaec002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ee682377336f02e54a18801daa3ba1ff8a99238f84b6c81a8cdff48b069fd89 0.600000000000 1425303 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": 965560, "vin": [ { "gen": { "height": 965550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ee682377336f02e54a18801daa3ba1ff8a99238f84b6c81a8cdff48b069fd89" } } ], "extra": [ 1, 83, 207, 99, 35, 187, 228, 219, 29, 75, 142, 76, 18, 162, 42, 28, 38, 44, 116, 142, 245, 93, 139, 85, 163, 199, 161, 138, 41, 158, 26, 174, 192, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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