Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bddcacada8c33d1c8168bb7095fe97affadefbc396a627c1abfa11ad083828d0

Tx prefix hash: 184192f6b267ca4b74386df18d44080d90454dc90f8083116c6fe8e97f847f37
Tx public key: 91b97d34bbeeadd9f3df8342cd3d5a0201c4c0f30585d100d6b969ebf5ebda17
Timestamp: 1758764685 Timestamp [UCT]: 2025-09-25 01:44:45 Age [y:d:h:m:s]: 00:012:20:59:49
Block: 1375814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9213 RingCT/type: yes/0
Extra: 0191b97d34bbeeadd9f3df8342cd3d5a0201c4c0f30585d100d6b969ebf5ebda17021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fd6aecaa07f4d36b1a6b80610ecd9115c6be1ff9c6211d7aabc4aec2185151f 0.600000000000 1863905 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": 1375824, "vin": [ { "gen": { "height": 1375814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fd6aecaa07f4d36b1a6b80610ecd9115c6be1ff9c6211d7aabc4aec2185151f" } } ], "extra": [ 1, 145, 185, 125, 52, 187, 238, 173, 217, 243, 223, 131, 66, 205, 61, 90, 2, 1, 196, 192, 243, 5, 133, 209, 0, 214, 185, 105, 235, 245, 235, 218, 23, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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