Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e24efd8588f5b1c81734a31b57991db874e473460d5e4ff5a8ce61a19e0b7ee1

Tx prefix hash: 3a2113d3d78dc246959aa6d10511d5edf104e58afa56aa95b32f318283895fb4
Tx public key: a6b150f4a73002e1c8482661bf87908544081c8cad412d5f053665e3ce0dff2c
Timestamp: 1703300784 Timestamp [UCT]: 2023-12-23 03:06:24 Age [y:d:h:m:s]: 01:124:07:22:30
Block: 919106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349987 RingCT/type: yes/0
Extra: 01a6b150f4a73002e1c8482661bf87908544081c8cad412d5f053665e3ce0dff2c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e58820a56fab031c524135c1aaf42551c2196a7ea1dd2444121f1c179625c2d 0.600000000000 1376770 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": 919116, "vin": [ { "gen": { "height": 919106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e58820a56fab031c524135c1aaf42551c2196a7ea1dd2444121f1c179625c2d" } } ], "extra": [ 1, 166, 177, 80, 244, 167, 48, 2, 225, 200, 72, 38, 97, 191, 135, 144, 133, 68, 8, 28, 140, 173, 65, 45, 95, 5, 54, 101, 227, 206, 13, 255, 44, 2, 17, 0, 0, 0, 4, 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