Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e89f02c75cf87028945918dc58ab001e5b8c5b79a08ec8eb6121cd4d8e7b6b65

Tx prefix hash: e18eddf4431104c101a149b0fcf6a172cc6c1081650cb8134f878a0d8702abb1
Tx public key: 6b23fe972e5341c8ede5bf71ae6bab39e935b0c07ccdcbd7576a609e52df8ea4
Timestamp: 1715833165 Timestamp [UCT]: 2024-05-16 04:19:25 Age [y:d:h:m:s]: 00:284:07:41:54
Block: 1023017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203184 RingCT/type: yes/0
Extra: 016b23fe972e5341c8ede5bf71ae6bab39e935b0c07ccdcbd7576a609e52df8ea402110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e73cfdc7cc9821b15b1513c6399e754d6926f54aa72393241d04b0c09f62fde 0.600000000000 1487784 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": 1023027, "vin": [ { "gen": { "height": 1023017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e73cfdc7cc9821b15b1513c6399e754d6926f54aa72393241d04b0c09f62fde" } } ], "extra": [ 1, 107, 35, 254, 151, 46, 83, 65, 200, 237, 229, 191, 113, 174, 107, 171, 57, 233, 53, 176, 192, 124, 205, 203, 215, 87, 106, 96, 158, 82, 223, 142, 164, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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