Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1028428b84fb42e2433759b7d34af802e2d104820ec800e17d9b7326f7b4b850

Tx prefix hash: 11120cf3329e966b8f868653b077d60b2e28c2ebb5d40960371ecd2ac87bb77a
Tx public key: c857264f2c3a9291008a3d951fccf13d37bd9cb052086c7bce2f280dd4151c32
Timestamp: 1595255036 Timestamp [UCT]: 2020-07-20 14:23:56 Age [y:d:h:m:s]: 04:130:00:15:02
Block: 118569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1043613 RingCT/type: yes/0
Extra: 01c857264f2c3a9291008a3d951fccf13d37bd9cb052086c7bce2f280dd4151c3202110000001f4943cd9f000000000000000000

1 output(s) for total of 248.391963811000 dcy

stealth address amount amount idx
00: 2d1740372b3a4d2e74527f3aad4a86a6af4a482d9cad25b17163cf5bbaab4ac1 248.391963811000 202383 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": 118579, "vin": [ { "gen": { "height": 118569 } } ], "vout": [ { "amount": 248391963811, "target": { "key": "2d1740372b3a4d2e74527f3aad4a86a6af4a482d9cad25b17163cf5bbaab4ac1" } } ], "extra": [ 1, 200, 87, 38, 79, 44, 58, 146, 145, 0, 138, 61, 149, 31, 204, 241, 61, 55, 189, 156, 176, 82, 8, 108, 123, 206, 47, 40, 13, 212, 21, 28, 50, 2, 17, 0, 0, 0, 31, 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