Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 904fc28c49d733c80830fbceba6ff9b5bc8c4f791b53d2c8d003192cf9f995cf

Tx prefix hash: 06937695f9c6949cca3c8b7175f2dbfc13096953bbe9ab2bf417e159b58ed6e8
Tx public key: a6c186b58f911a5c1d68c3dda99c729bb547579d4ecc28d502d433fd99790e82
Timestamp: 1736472129 Timestamp [UCT]: 2025-01-10 01:22:09 Age [y:d:h:m:s]: 00:158:16:13:05
Block: 1193978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113126 RingCT/type: yes/0
Extra: 01a6c186b58f911a5c1d68c3dda99c729bb547579d4ecc28d502d433fd99790e820211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9b5335e5a8730ee905f0d86475805a564feedc0021d6a6dd1bae5c523029afc 0.600000000000 1680545 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": 1193988, "vin": [ { "gen": { "height": 1193978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9b5335e5a8730ee905f0d86475805a564feedc0021d6a6dd1bae5c523029afc" } } ], "extra": [ 1, 166, 193, 134, 181, 143, 145, 26, 92, 29, 104, 195, 221, 169, 156, 114, 155, 181, 71, 87, 157, 78, 204, 40, 213, 2, 212, 51, 253, 153, 121, 14, 130, 2, 17, 0, 0, 0, 3, 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