Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3c3a4fd0b6b4eef335666a93a9ed2e1c3c1eb3c8fa581bf309554853167a0a1

Tx prefix hash: 05dd8cbe0918b16a7200f7c234e82687ec12dcaef473df129ee71c2cecbe5296
Tx public key: 8a348aef602a5d8731c66c97a55092acf1d9a8a642f8490efdae83fcd7301c97
Timestamp: 1710400285 Timestamp [UCT]: 2024-03-14 07:11:25 Age [y:d:h:m:s]: 01:061:07:13:33
Block: 977993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304814 RingCT/type: yes/0
Extra: 018a348aef602a5d8731c66c97a55092acf1d9a8a642f8490efdae83fcd7301c970211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71a4f54b9eb9664a0d07858c6758d0eabaf3959b783a3b7c58dc797c84e4c0bc 0.600000000000 1438002 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": 978003, "vin": [ { "gen": { "height": 977993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71a4f54b9eb9664a0d07858c6758d0eabaf3959b783a3b7c58dc797c84e4c0bc" } } ], "extra": [ 1, 138, 52, 138, 239, 96, 42, 93, 135, 49, 198, 108, 151, 165, 80, 146, 172, 241, 217, 168, 166, 66, 248, 73, 14, 253, 174, 131, 252, 215, 48, 28, 151, 2, 17, 0, 0, 0, 5, 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