Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e223cfe08d822ade7ec0724bc21e8f3fd19dce5979685685f7febea75a610b53

Tx prefix hash: b021eee4eed3609156ebcbee80716748c995afa74eeb2495a2b95d6f4bcca535
Tx public key: 8989124b0a3bc3a9490dc18be97cc8f85639a366ee0e78a24f7577ed7c9d7b2f
Timestamp: 1625817061 Timestamp [UCT]: 2021-07-09 07:51:01 Age [y:d:h:m:s]: 03:141:20:40:51
Block: 290699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 871896 RingCT/type: yes/0
Extra: 018989124b0a3bc3a9490dc18be97cc8f85639a366ee0e78a24f7577ed7c9d7b2f021100000139d2fc4d28000000000000000000

1 output(s) for total of 66.802704043000 dcy

stealth address amount amount idx
00: b8b6d7b163f1ae12d7dd7b34e594b3edc5d1d34ea01b3e5b0daf98b1c9940325 66.802704043000 608779 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": 290709, "vin": [ { "gen": { "height": 290699 } } ], "vout": [ { "amount": 66802704043, "target": { "key": "b8b6d7b163f1ae12d7dd7b34e594b3edc5d1d34ea01b3e5b0daf98b1c9940325" } } ], "extra": [ 1, 137, 137, 18, 75, 10, 59, 195, 169, 73, 13, 193, 139, 233, 124, 200, 248, 86, 57, 163, 102, 238, 14, 120, 162, 79, 117, 119, 237, 124, 157, 123, 47, 2, 17, 0, 0, 1, 57, 210, 252, 77, 40, 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