Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a7765f84f142bb49acde0e1b4cc39e0da03efc432b10868757136b98b44811c

Tx prefix hash: aa63e25175391f968b1bf1525483d11aed2ec1b61ba42316229f2c48a9f7f90f
Tx public key: 6ea5399d10ae82293963b328f7f6fcd01ae9052d2dc9fa7939459c3ac5123389
Timestamp: 1699945024 Timestamp [UCT]: 2023-11-14 06:57:04 Age [y:d:h:m:s]: 01:362:17:46:46
Block: 891284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518162 RingCT/type: yes/0
Extra: 016ea5399d10ae82293963b328f7f6fcd01ae9052d2dc9fa7939459c3ac512338902110000000233af99f4000000000000000000

1 output(s) for total of 0.683606391000 dcy

stealth address amount amount idx
00: 754f34fe91d44d693681c26484059bc0f22c3c41c5210ed96b02ebe73f9836b0 0.683606391000 1347321 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": 891294, "vin": [ { "gen": { "height": 891284 } } ], "vout": [ { "amount": 683606391, "target": { "key": "754f34fe91d44d693681c26484059bc0f22c3c41c5210ed96b02ebe73f9836b0" } } ], "extra": [ 1, 110, 165, 57, 157, 16, 174, 130, 41, 57, 99, 179, 40, 247, 246, 252, 208, 26, 233, 5, 45, 45, 201, 250, 121, 57, 69, 156, 58, 197, 18, 51, 137, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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