Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02a94990c387feaf27e62525e3a0f5b56d073ce2744fe6247d224016d2416755

Tx prefix hash: 5bdf2303d641352799180563ccc736aa3ce3b196742a5c66ba70cd34d9552f0e
Tx public key: e806cc6adf3c081cbb6f3140d14a83e7d328d9274900f1852539b8504ddb0129
Timestamp: 1647649593 Timestamp [UCT]: 2022-03-19 00:26:33 Age [y:d:h:m:s]: 02:327:18:54:48
Block: 461449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 753545 RingCT/type: yes/0
Extra: 01e806cc6adf3c081cbb6f3140d14a83e7d328d9274900f1852539b8504ddb0129021100000003bf7ee4e7000000000000000000

1 output(s) for total of 18.156334212000 dcy

stealth address amount amount idx
00: 682cbd7c357570e76cc9e7983d51f1a1f1d5d21f7227378b0bfe179c3b077e3d 18.156334212000 878692 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": 461459, "vin": [ { "gen": { "height": 461449 } } ], "vout": [ { "amount": 18156334212, "target": { "key": "682cbd7c357570e76cc9e7983d51f1a1f1d5d21f7227378b0bfe179c3b077e3d" } } ], "extra": [ 1, 232, 6, 204, 106, 223, 60, 8, 28, 187, 111, 49, 64, 209, 74, 131, 231, 211, 40, 217, 39, 73, 0, 241, 133, 37, 57, 184, 80, 77, 219, 1, 41, 2, 17, 0, 0, 0, 3, 191, 126, 228, 231, 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