Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 488e461ca8aa5bb5adc1916d6b34273a51524512be445b2b2e70b98ce500b60a

Tx prefix hash: a96b2a4bf35873851bea97cb2ac31acb3cae1e9741ae5f0dfd3a98ff4d3318d0
Tx public key: d3879cd1d7ca0b3b0b8f25e7a271a87fe08f320136264e939d3cfb9928c98ee5
Timestamp: 1582295159 Timestamp [UCT]: 2020-02-21 14:25:59 Age [y:d:h:m:s]: 05:084:05:46:18
Block: 69640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1213334 RingCT/type: yes/0
Extra: 01d3879cd1d7ca0b3b0b8f25e7a271a87fe08f320136264e939d3cfb9928c98ee502110000000156c366d3000000000000000000

1 output(s) for total of 360.802229410000 dcy

stealth address amount amount idx
00: 0df55488f2b03ea8def329912009f36addbdcf6280626828e5b8847f5b99c475 360.802229410000 128416 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": 69650, "vin": [ { "gen": { "height": 69640 } } ], "vout": [ { "amount": 360802229410, "target": { "key": "0df55488f2b03ea8def329912009f36addbdcf6280626828e5b8847f5b99c475" } } ], "extra": [ 1, 211, 135, 156, 209, 215, 202, 11, 59, 11, 143, 37, 231, 162, 113, 168, 127, 224, 143, 50, 1, 54, 38, 78, 147, 157, 60, 251, 153, 40, 201, 142, 229, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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