Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 060f33b6b6619e3378afc05a0218e859c86a91fd668c8114c5f82834fd70ce92

Tx prefix hash: 17eab839932326ed5eeae074e4f8846efb52141ec0ab600610799a18d136361c
Tx public key: ac1193b5b474bb1d739e80b1b3ee97d87f19cd2d3f08d5600f04aa9f794abcec
Timestamp: 1743467679 Timestamp [UCT]: 2025-04-01 00:34:39 Age [y:d:h:m:s]: 00:234:16:21:36
Block: 1251628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165451 RingCT/type: yes/0
Extra: 01ac1193b5b474bb1d739e80b1b3ee97d87f19cd2d3f08d5600f04aa9f794abcec021100000006a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96b31bef4a906716d515f2a62873d4c9369d1bd77ecb3eb2a63858401cd83b0b 0.600000000000 1738697 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": 1251638, "vin": [ { "gen": { "height": 1251628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96b31bef4a906716d515f2a62873d4c9369d1bd77ecb3eb2a63858401cd83b0b" } } ], "extra": [ 1, 172, 17, 147, 181, 180, 116, 187, 29, 115, 158, 128, 177, 179, 238, 151, 216, 127, 25, 205, 45, 63, 8, 213, 96, 15, 4, 170, 159, 121, 74, 188, 236, 2, 17, 0, 0, 0, 6, 162, 237, 1, 107, 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