Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ed8032f41002203d58d601b678616ba3956b5263162ecd049ddbdb5aef13c51

Tx prefix hash: 0b4bc0b7507a47f6cf30309268594563b0ca2432b2071d16c4f15552eb567484
Tx public key: 7b05f667365a7f76dfc821c32edc72b8ef0a833e45cb52772353372c2ec4c7c4
Timestamp: 1633244385 Timestamp [UCT]: 2021-10-03 06:59:45 Age [y:d:h:m:s]: 03:096:15:53:37
Block: 345645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 846107 RingCT/type: yes/0
Extra: 017b05f667365a7f76dfc821c32edc72b8ef0a833e45cb52772353372c2ec4c7c402110000016e5d7cc334000000000000000000

1 output(s) for total of 43.927355647000 dcy

stealth address amount amount idx
00: be88121b2032e352f4c9c577bdfb49c0c682dc6fa43969003868fdf1a3a1ddb3 43.927355647000 709003 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": 345655, "vin": [ { "gen": { "height": 345645 } } ], "vout": [ { "amount": 43927355647, "target": { "key": "be88121b2032e352f4c9c577bdfb49c0c682dc6fa43969003868fdf1a3a1ddb3" } } ], "extra": [ 1, 123, 5, 246, 103, 54, 90, 127, 118, 223, 200, 33, 195, 46, 220, 114, 184, 239, 10, 131, 62, 69, 203, 82, 119, 35, 83, 55, 44, 46, 196, 199, 196, 2, 17, 0, 0, 1, 110, 93, 124, 195, 52, 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