Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5cf6bd6723d138203d2e30fa8b82ec7c594e5ff27b2baaca7928f905bf8dc2d

Tx prefix hash: 3cbb4c6a73e6d1838d753828dd0496265731d4ceb6a09f64884af083c3417feb
Tx public key: c8717deb913c362c0a4604d42e86697064eab7b6ce3d052e9890a87ffab79b14
Timestamp: 1733762001 Timestamp [UCT]: 2024-12-09 16:33:21 Age [y:d:h:m:s]: 00:100:19:47:10
Block: 1171555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71857 RingCT/type: yes/0
Extra: 01c8717deb913c362c0a4604d42e86697064eab7b6ce3d052e9890a87ffab79b14021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0dfbef7965681194ac2087d74de1d795aa78ecb98f5016f91c15d99fdb3bca9 0.600000000000 1657328 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": 1171565, "vin": [ { "gen": { "height": 1171555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0dfbef7965681194ac2087d74de1d795aa78ecb98f5016f91c15d99fdb3bca9" } } ], "extra": [ 1, 200, 113, 125, 235, 145, 60, 54, 44, 10, 70, 4, 212, 46, 134, 105, 112, 100, 234, 183, 182, 206, 61, 5, 46, 152, 144, 168, 127, 250, 183, 155, 20, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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