Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcd283339728fbe02a48ea670a8ecb8172034063ffc5d64a80e96d293624c7af

Tx prefix hash: 0a3031a2cc4330d3b44eed649fb19ea72de891753d17582bdf8068837e5ce100
Tx public key: a095fde11d7461d05b4479cfe370501d5a72660f28bbccec522ee52bd2c1c9f1
Timestamp: 1635302702 Timestamp [UCT]: 2021-10-27 02:45:02 Age [y:d:h:m:s]: 03:103:22:20:37
Block: 361270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 852474 RingCT/type: yes/0
Extra: 01a095fde11d7461d05b4479cfe370501d5a72660f28bbccec522ee52bd2c1c9f10211000000171154028c000000000000000000

1 output(s) for total of 38.990870098000 dcy

stealth address amount amount idx
00: b161bc8cc79fd3cb1aeaf8825bf3d326ae7ea50c1ac16eb4e14ab0db25782a7f 38.990870098000 735061 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": 361280, "vin": [ { "gen": { "height": 361270 } } ], "vout": [ { "amount": 38990870098, "target": { "key": "b161bc8cc79fd3cb1aeaf8825bf3d326ae7ea50c1ac16eb4e14ab0db25782a7f" } } ], "extra": [ 1, 160, 149, 253, 225, 29, 116, 97, 208, 91, 68, 121, 207, 227, 112, 80, 29, 90, 114, 102, 15, 40, 187, 204, 236, 82, 46, 229, 43, 210, 193, 201, 241, 2, 17, 0, 0, 0, 23, 17, 84, 2, 140, 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