Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76ab8ccdfc15321dc40ca85f4321a5f38ab184d11d7fe9047c2cde262cdb5a32

Tx prefix hash: d197f64a519b2303d1291a6af68f101e09ae435e62750f10498373eb0c1f46ac
Tx public key: 0abd92d2901084040247b578ea2ca323efc7ca22978b53a9ad897f425caad0cb
Timestamp: 1588557204 Timestamp [UCT]: 2020-05-04 01:53:24 Age [y:d:h:m:s]: 04:274:11:55:19
Block: 98415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111397 RingCT/type: yes/0
Extra: 010abd92d2901084040247b578ea2ca323efc7ca22978b53a9ad897f425caad0cb0211000000064943cd9f000000000000000000

1 output(s) for total of 289.679999721000 dcy

stealth address amount amount idx
00: 6e1f8fff029d2b16704216de514a945cfd3a32e2d838496e71cac74904641ad3 289.679999721000 173914 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": 98425, "vin": [ { "gen": { "height": 98415 } } ], "vout": [ { "amount": 289679999721, "target": { "key": "6e1f8fff029d2b16704216de514a945cfd3a32e2d838496e71cac74904641ad3" } } ], "extra": [ 1, 10, 189, 146, 210, 144, 16, 132, 4, 2, 71, 181, 120, 234, 44, 163, 35, 239, 199, 202, 34, 151, 139, 83, 169, 173, 137, 127, 66, 92, 170, 208, 203, 2, 17, 0, 0, 0, 6, 73, 67, 205, 159, 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