Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8a1143fa8980a27bffe55d652d87d2bd28dbd8b1472964a066f4d5739f09697

Tx prefix hash: 71c8710fc278e5426627ac802bed680c230293630dc58303ade5e0194dc72ea0
Tx public key: 5b8acc6782f7ef65a3809ad3cb2c4c8a054bd93d8650f1071f5fef6aa285cac5
Timestamp: 1715604096 Timestamp [UCT]: 2024-05-13 12:41:36 Age [y:d:h:m:s]: 00:241:15:05:34
Block: 1021136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172908 RingCT/type: yes/0
Extra: 015b8acc6782f7ef65a3809ad3cb2c4c8a054bd93d8650f1071f5fef6aa285cac50211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8488def4cec3c29b3516d9878ca57687d93ea1ae2ad2770bd986064af0e06913 0.600000000000 1485359 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": 1021146, "vin": [ { "gen": { "height": 1021136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8488def4cec3c29b3516d9878ca57687d93ea1ae2ad2770bd986064af0e06913" } } ], "extra": [ 1, 91, 138, 204, 103, 130, 247, 239, 101, 163, 128, 154, 211, 203, 44, 76, 138, 5, 75, 217, 61, 134, 80, 241, 7, 31, 95, 239, 106, 162, 133, 202, 197, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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