Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 554ad21c4c30a976486211ebfbd10b46026c86324f83ab8e6490afc5fc5295bc

Tx prefix hash: bd9934283a5a7b30c33f5828e83db8f956f63d01924a87e4abe5bc688fa85213
Tx public key: 0104e29089a2b0fd02889aa510ee3f9ac70b2fb63db7542662d95951d6e88dd1
Timestamp: 1608916318 Timestamp [UCT]: 2020-12-25 17:11:58 Age [y:d:h:m:s]: 04:077:13:24:40
Block: 169288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1068214 RingCT/type: yes/0
Extra: 010104e29089a2b0fd02889aa510ee3f9ac70b2fb63db7542662d95951d6e88dd102110000076e27e2517e000000000000000000

1 output(s) for total of 168.700650782000 dcy

stealth address amount amount idx
00: 1089c741db3c5776d171b7ca650aeb48026148bbff78e3d7dd91f806a0a92c9d 168.700650782000 315683 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": 169298, "vin": [ { "gen": { "height": 169288 } } ], "vout": [ { "amount": 168700650782, "target": { "key": "1089c741db3c5776d171b7ca650aeb48026148bbff78e3d7dd91f806a0a92c9d" } } ], "extra": [ 1, 1, 4, 226, 144, 137, 162, 176, 253, 2, 136, 154, 165, 16, 238, 63, 154, 199, 11, 47, 182, 61, 183, 84, 38, 98, 217, 89, 81, 214, 232, 141, 209, 2, 17, 0, 0, 7, 110, 39, 226, 81, 126, 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