Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5923080ac71874c31e1f8662add93c30694035aa66281d112a562ed225ac1023

Tx prefix hash: a3080aa3272315d5ab9f48ac1dc7ac1e71da4a68272a5643440fa699be904c3a
Tx public key: 005081b46cf430fc74e9e99a56bde1fa0e240bc6d7d6fe3bd3edb259ea0abbbf
Timestamp: 1735204629 Timestamp [UCT]: 2024-12-26 09:17:09 Age [y:d:h:m:s]: 00:089:19:05:13
Block: 1183492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63937 RingCT/type: yes/0
Extra: 01005081b46cf430fc74e9e99a56bde1fa0e240bc6d7d6fe3bd3edb259ea0abbbf0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b161e44672a64a56d95a96092920ec309eb24480cac74b5767153d11b0d18c8a 0.600000000000 1669937 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": 1183502, "vin": [ { "gen": { "height": 1183492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b161e44672a64a56d95a96092920ec309eb24480cac74b5767153d11b0d18c8a" } } ], "extra": [ 1, 0, 80, 129, 180, 108, 244, 48, 252, 116, 233, 233, 154, 86, 189, 225, 250, 14, 36, 11, 198, 215, 214, 254, 59, 211, 237, 178, 89, 234, 10, 187, 191, 2, 17, 0, 0, 0, 2, 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