Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b685166580558614e2f3381c154d32cb12c1d0f9f40895c457ca7d5adb02f3ae

Tx prefix hash: 38a9c306a287a7f673c3128253c1486d4ae8da7b97f271975955318909592b3e
Tx public key: fbda09bcef7fc6db70b8224e35a1b5ee6608bd3d0a0c251523df919d7ad6a185
Timestamp: 1752729632 Timestamp [UCT]: 2025-07-17 05:20:32 Age [y:d:h:m:s]: 00:126:02:40:57
Block: 1327202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88903 RingCT/type: yes/0
Extra: 01fbda09bcef7fc6db70b8224e35a1b5ee6608bd3d0a0c251523df919d7ad6a18502110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed9c4e986ffed43881f8c2e7dfefcde17f1206423c9911186cb073e83bd55143 0.600000000000 1814955 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": 1327212, "vin": [ { "gen": { "height": 1327202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed9c4e986ffed43881f8c2e7dfefcde17f1206423c9911186cb073e83bd55143" } } ], "extra": [ 1, 251, 218, 9, 188, 239, 127, 198, 219, 112, 184, 34, 78, 53, 161, 181, 238, 102, 8, 189, 61, 10, 12, 37, 21, 35, 223, 145, 157, 122, 214, 161, 133, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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