Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 007506fff165079165498e015b8075d81215b32cc8a37fb6d3f8fccee9a082d2

Tx prefix hash: 0eb6e2dfd01739eae58088b5f06ab07e5514953d80cea5cad1d58f5f6c02c1a6
Tx public key: 863fddd895d410ca916a2f2445f170c64f1972da3d14d8fd60907b8b7171d27d
Timestamp: 1732356435 Timestamp [UCT]: 2024-11-23 10:07:15 Age [y:d:h:m:s]: 00:000:12:10:26
Block: 1159899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358 RingCT/type: yes/0
Extra: 01863fddd895d410ca916a2f2445f170c64f1972da3d14d8fd60907b8b7171d27d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 763ccbab67a6cd58c83f7fa2b3ea2f973346b019380a198ec9f66ba76bfae333 0.600000000000 1645538 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": 1159909, "vin": [ { "gen": { "height": 1159899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "763ccbab67a6cd58c83f7fa2b3ea2f973346b019380a198ec9f66ba76bfae333" } } ], "extra": [ 1, 134, 63, 221, 216, 149, 212, 16, 202, 145, 106, 47, 36, 69, 241, 112, 198, 79, 25, 114, 218, 61, 20, 216, 253, 96, 144, 123, 139, 113, 113, 210, 125, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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