Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2c4e0eeadc8f988c9d75d8c999eb83f263ea18a5084e689d8c8a94194acac38

Tx prefix hash: a24c465cc1a0cf810247eb4304e17242c2cbcb0e1a101d5b62390815a3e783d2
Tx public key: ee8663ea5e3099af55581f60bdeb8e92deb66a20e6146ea2e3da5dba473eed1e
Timestamp: 1723895905 Timestamp [UCT]: 2024-08-17 11:58:25 Age [y:d:h:m:s]: 01:139:00:40:46
Block: 1089862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357893 RingCT/type: yes/0
Extra: 01ee8663ea5e3099af55581f60bdeb8e92deb66a20e6146ea2e3da5dba473eed1e02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 946f59a97fa71e39aae4f1ab44afc48199fd147aabba1b28e71d22ffbc24dac5 0.600000000000 1564485 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": 1089872, "vin": [ { "gen": { "height": 1089862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "946f59a97fa71e39aae4f1ab44afc48199fd147aabba1b28e71d22ffbc24dac5" } } ], "extra": [ 1, 238, 134, 99, 234, 94, 48, 153, 175, 85, 88, 31, 96, 189, 235, 142, 146, 222, 182, 106, 32, 230, 20, 110, 162, 227, 218, 93, 186, 71, 62, 237, 30, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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