Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3341ec162661d32cc50cdea512e36e168943c1271329ec3d5fea10283e66b455

Tx prefix hash: cbddc9511d9e84e74cba8ea8dfe60b580111b62ce44942714ce2c2e1a2390978
Tx public key: 693170b939dd264a7eb5fbf9970266e1be246ab53749240b0ef5a403ec793f6c
Timestamp: 1764973734 Timestamp [UCT]: 2025-12-05 22:28:54 Age [y:d:h:m:s]: 00:000:02:09:41
Block: 1427273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59 RingCT/type: yes/0
Extra: 01693170b939dd264a7eb5fbf9970266e1be246ab53749240b0ef5a403ec793f6c02110000000dd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1f32f6e5e65d31a1c42a3e2e8b6ea487a61d49cd9e6347ee8431f51a6a581e6 0.600000000000 1915974 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": 1427283, "vin": [ { "gen": { "height": 1427273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1f32f6e5e65d31a1c42a3e2e8b6ea487a61d49cd9e6347ee8431f51a6a581e6" } } ], "extra": [ 1, 105, 49, 112, 185, 57, 221, 38, 74, 126, 181, 251, 249, 151, 2, 102, 225, 190, 36, 106, 181, 55, 73, 36, 11, 14, 245, 164, 3, 236, 121, 63, 108, 2, 17, 0, 0, 0, 13, 214, 225, 157, 124, 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