Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 569d3ab0139023142fff7314f78675c0e36caf91e2407a425dc66619d6be8e8d

Tx prefix hash: 2cda61ed64c2a3de735b6fdb4f5e1443a72cabe9c91ec5bc0c82b4ea950bb517
Tx public key: b8f731a45c99fb8578a0de3f33b8a21fb54dc9ca16bf962ced6dcc6bb9708d2b
Timestamp: 1729744526 Timestamp [UCT]: 2024-10-24 04:35:26 Age [y:d:h:m:s]: 00:168:18:29:09
Block: 1138314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120412 RingCT/type: yes/0
Extra: 01b8f731a45c99fb8578a0de3f33b8a21fb54dc9ca16bf962ced6dcc6bb9708d2b0211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 844d64234b5315b11daf1e98aa23b05cb9569f02845b1ccbecb52e3653b2ccad 0.600000000000 1621951 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": 1138324, "vin": [ { "gen": { "height": 1138314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "844d64234b5315b11daf1e98aa23b05cb9569f02845b1ccbecb52e3653b2ccad" } } ], "extra": [ 1, 184, 247, 49, 164, 92, 153, 251, 133, 120, 160, 222, 63, 51, 184, 162, 31, 181, 77, 201, 202, 22, 191, 150, 44, 237, 109, 204, 107, 185, 112, 141, 43, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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