Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87f7916eda821796f820ad5ae836d21250a4efa89d50ce216e97557b713f01c4

Tx prefix hash: f136141a925f9c802f6be0a9e008fcacea0f9125c174a46a226e558644497036
Tx public key: 052d9e2d815308d06ecfd0f0974d05e15469e257308e8b4c9b69008118f10b8a
Timestamp: 1755392395 Timestamp [UCT]: 2025-08-17 00:59:55 Age [y:d:h:m:s]: 00:092:15:25:59
Block: 1348172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66033 RingCT/type: yes/0
Extra: 01052d9e2d815308d06ecfd0f0974d05e15469e257308e8b4c9b69008118f10b8a021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 175fd40cf680a727b62a3b28d82da366d42f0a24c358f17c310b01083adfd4b9 0.600000000000 1836095 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": 1348182, "vin": [ { "gen": { "height": 1348172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "175fd40cf680a727b62a3b28d82da366d42f0a24c358f17c310b01083adfd4b9" } } ], "extra": [ 1, 5, 45, 158, 45, 129, 83, 8, 208, 110, 207, 208, 240, 151, 77, 5, 225, 84, 105, 226, 87, 48, 142, 139, 76, 155, 105, 0, 129, 24, 241, 11, 138, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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