Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3f5c1efd81eb940649319c97b8754e61d80124ebd0d3a83f43e54754b0f4046

Tx prefix hash: ce97015616752a61bfe08b5c900664547a8036caa3bf39f12318c2b32a3ff8bc
Tx public key: 6c3609c126356f3fad6af78841f9b9a0fffffff75fe769f55974e0b70ef1743d
Timestamp: 1732725797 Timestamp [UCT]: 2024-11-27 16:43:17 Age [y:d:h:m:s]: 00:140:11:25:55
Block: 1162953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100215 RingCT/type: yes/0
Extra: 016c3609c126356f3fad6af78841f9b9a0fffffff75fe769f55974e0b70ef1743d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ef0f6ab2d94a4627c39a4d94ddb2773f88084b2f4e3cf0c441ee8f97e12b7e8 0.600000000000 1648616 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": 1162963, "vin": [ { "gen": { "height": 1162953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ef0f6ab2d94a4627c39a4d94ddb2773f88084b2f4e3cf0c441ee8f97e12b7e8" } } ], "extra": [ 1, 108, 54, 9, 193, 38, 53, 111, 63, 173, 106, 247, 136, 65, 249, 185, 160, 255, 255, 255, 247, 95, 231, 105, 245, 89, 116, 224, 183, 14, 241, 116, 61, 2, 17, 0, 0, 0, 2, 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