Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 887d5ebc1360cd4b69ef92337d99d8e677b8e1736c2ecc42a501b6c00dacaec2

Tx prefix hash: 12309599eb34207722c4a30e06b89c29e3eee59c7a0bd1caf2ca4740e96697bb
Tx public key: dc3d917b3fbdc7e6e5834347ecee88e2a98990b80973e8542d7af345b4dcb12f
Timestamp: 1587357133 Timestamp [UCT]: 2020-04-20 04:32:13 Age [y:d:h:m:s]: 04:294:07:48:00
Block: 94542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119526 RingCT/type: yes/0
Extra: 01dc3d917b3fbdc7e6e5834347ecee88e2a98990b80973e8542d7af345b4dcb12f02110000010137fb5df4000000000000000000

1 output(s) for total of 298.362252097000 dcy

stealth address amount amount idx
00: 45b9a56aeccd3dd16bb2093fbd07aa357d1cc01f4bcd96d46d09ce84e8b02629 298.362252097000 168104 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": 94552, "vin": [ { "gen": { "height": 94542 } } ], "vout": [ { "amount": 298362252097, "target": { "key": "45b9a56aeccd3dd16bb2093fbd07aa357d1cc01f4bcd96d46d09ce84e8b02629" } } ], "extra": [ 1, 220, 61, 145, 123, 63, 189, 199, 230, 229, 131, 67, 71, 236, 238, 136, 226, 169, 137, 144, 184, 9, 115, 232, 84, 45, 122, 243, 69, 180, 220, 177, 47, 2, 17, 0, 0, 1, 1, 55, 251, 93, 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