Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5fa7d4e79358c7f32bf01a2ba90decf8744fd6cc0b70a5f0060189c9e6c65ff

Tx prefix hash: 183fc098892b0b465fa280261ff2b5e643448df0882ab5b419603e762366931a
Tx public key: 923f8514a3aae275ed932abd71cacd54baf3e59a6d75fe88689d8fa29ab67d60
Timestamp: 1639459832 Timestamp [UCT]: 2021-12-14 05:30:32 Age [y:d:h:m:s]: 03:055:01:10:54
Block: 395119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 818055 RingCT/type: yes/0
Extra: 01923f8514a3aae275ed932abd71cacd54baf3e59a6d75fe88689d8fa29ab67d6002110000000375e655a0000000000000000000

1 output(s) for total of 30.116679683000 dcy

stealth address amount amount idx
00: b2db6ae9a7679cf288ec5bc2bacda35105a2bf1a74f5798d52871e8c460ac17e 30.116679683000 792930 of 0

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": 395129, "vin": [ { "gen": { "height": 395119 } } ], "vout": [ { "amount": 30116679683, "target": { "key": "b2db6ae9a7679cf288ec5bc2bacda35105a2bf1a74f5798d52871e8c460ac17e" } } ], "extra": [ 1, 146, 63, 133, 20, 163, 170, 226, 117, 237, 147, 42, 189, 113, 202, 205, 84, 186, 243, 229, 154, 109, 117, 254, 136, 104, 157, 143, 162, 154, 182, 125, 96, 2, 17, 0, 0, 0, 3, 117, 230, 85, 160, 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