Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3bcecde87390ce1349a36122b06d15117490bd966f3f94118537ea3b3b32dba

Tx prefix hash: 9b139b4cc77e91dcc910fe395656e9c0c34ed2213fb55ff41247d4687332b60d
Tx public key: 6126a284a3ab4814d661a3d0d787e37e76859241f773f9eb6c8a2a1b84b9563d
Timestamp: 1715476264 Timestamp [UCT]: 2024-05-12 01:11:04 Age [y:d:h:m:s]: 01:179:00:01:00
Block: 1020082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386504 RingCT/type: yes/0
Extra: 016126a284a3ab4814d661a3d0d787e37e76859241f773f9eb6c8a2a1b84b9563d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7366e3a233af3b159455c6ad1f61f9a57e0a57ede5e5083b597a803b2b6f8611 0.600000000000 1484141 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": 1020092, "vin": [ { "gen": { "height": 1020082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7366e3a233af3b159455c6ad1f61f9a57e0a57ede5e5083b597a803b2b6f8611" } } ], "extra": [ 1, 97, 38, 162, 132, 163, 171, 72, 20, 214, 97, 163, 208, 215, 135, 227, 126, 118, 133, 146, 65, 247, 115, 249, 235, 108, 138, 42, 27, 132, 185, 86, 61, 2, 17, 0, 0, 0, 3, 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