Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62bed63ca5f20062eff9614109cec6a504a2837ef6225a2e90e0a55986ede3b9

Tx prefix hash: 36210ced11c345a9d4baf64fc61356541b415847d6737d7e66f597ef32ab0073
Tx public key: e6e8613dce59d3e192e15e4c171272775f2ab1bb703301f1ec0d8c6ddeb05763
Timestamp: 1706021441 Timestamp [UCT]: 2024-01-23 14:50:41 Age [y:d:h:m:s]: 01:078:12:50:14
Block: 941640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317231 RingCT/type: yes/0
Extra: 01e6e8613dce59d3e192e15e4c171272775f2ab1bb703301f1ec0d8c6ddeb057630211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac489f2347ad68f5e4aa074c3a9a5744c5a17c16c1392062108eeb475a7b42a8 0.600000000000 1399796 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": 941650, "vin": [ { "gen": { "height": 941640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac489f2347ad68f5e4aa074c3a9a5744c5a17c16c1392062108eeb475a7b42a8" } } ], "extra": [ 1, 230, 232, 97, 61, 206, 89, 211, 225, 146, 225, 94, 76, 23, 18, 114, 119, 95, 42, 177, 187, 112, 51, 1, 241, 236, 13, 140, 109, 222, 176, 87, 99, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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