Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e9f78f4dcebf26de716d55902ef558d17df812102a24824c15ed1c4dfff696e

Tx prefix hash: 87f7e873a66bc2bde8355ad44d2e8cfc8c7047b5b52a8d3b4e3eaec9e3381a8a
Tx public key: 461860ad7fd908ac6b7d1bc58008fb5cb572f439d9c27d7305aa25156572695e
Timestamp: 1733870620 Timestamp [UCT]: 2024-12-10 22:43:40 Age [y:d:h:m:s]: 00:134:22:27:08
Block: 1172454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96237 RingCT/type: yes/0
Extra: 01461860ad7fd908ac6b7d1bc58008fb5cb572f439d9c27d7305aa25156572695e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50bc71ac89847d0ad2509152045136c72d5c91789cee1226447e184d886913b3 0.600000000000 1658345 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": 1172464, "vin": [ { "gen": { "height": 1172454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50bc71ac89847d0ad2509152045136c72d5c91789cee1226447e184d886913b3" } } ], "extra": [ 1, 70, 24, 96, 173, 127, 217, 8, 172, 107, 125, 27, 197, 128, 8, 251, 92, 181, 114, 244, 57, 217, 194, 125, 115, 5, 170, 37, 21, 101, 114, 105, 94, 2, 17, 0, 0, 0, 1, 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