Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f23f79f5534b37cfee7452ca41bc4086aaf59bb6c4e241a0c8588b4d713e7b19

Tx prefix hash: 5887510d2ff32f4d93aa5e3dd4c665ddcb297f858c6364bf8161e77e0768551e
Tx public key: 23182d36965da4b49c9f3a146dcfe69de8d2f72a50e9746054621ee7365dec90
Timestamp: 1736345254 Timestamp [UCT]: 2025-01-08 14:07:34 Age [y:d:h:m:s]: 01:019:01:49:06
Block: 1192927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271929 RingCT/type: yes/0
Extra: 0123182d36965da4b49c9f3a146dcfe69de8d2f72a50e9746054621ee7365dec9002110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b11f500c13acac5e41d649f1ca81fd9e1845daf9edcf7e3adc495b29df9fef2 0.600000000000 1679484 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": 1192937, "vin": [ { "gen": { "height": 1192927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b11f500c13acac5e41d649f1ca81fd9e1845daf9edcf7e3adc495b29df9fef2" } } ], "extra": [ 1, 35, 24, 45, 54, 150, 93, 164, 180, 156, 159, 58, 20, 109, 207, 230, 157, 232, 210, 247, 42, 80, 233, 116, 96, 84, 98, 30, 231, 54, 93, 236, 144, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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