Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12fe205fafca7750a762522e0b18cb0a663d3b83d6783211d160f5e793e7d01c

Tx prefix hash: 9390159b9ee6e4439924b9b6e9fe8f9e77d417097bd3523db8d1cee0ded2d161
Tx public key: d58bc861bbc630c351e1d47280575de9e0f335d02e2a9221565753893ffa2dd8
Timestamp: 1752190333 Timestamp [UCT]: 2025-07-10 23:32:13 Age [y:d:h:m:s]: 00:181:15:03:01
Block: 1322925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128472 RingCT/type: yes/0
Extra: 01d58bc861bbc630c351e1d47280575de9e0f335d02e2a9221565753893ffa2dd80211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cec0fdc2b2b8fe762cc09229b1b0c5142bb40f55c5d02913cb77cb10a8d23528 0.600000000000 1810658 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": 1322935, "vin": [ { "gen": { "height": 1322925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cec0fdc2b2b8fe762cc09229b1b0c5142bb40f55c5d02913cb77cb10a8d23528" } } ], "extra": [ 1, 213, 139, 200, 97, 187, 198, 48, 195, 81, 225, 212, 114, 128, 87, 93, 233, 224, 243, 53, 208, 46, 42, 146, 33, 86, 87, 83, 137, 63, 250, 45, 216, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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