Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9a64bf2e447c14356e73bdb087b7294ab36a3a61073f401cab3a6a56f1457d7

Tx prefix hash: ea64c6f77773c069013b4f7e3176537c06ddc33f0d317f9184a6cc410d6ce699
Tx public key: a54b9fd9d876991c6e79d0cb3461147610d44f32fbecc4539e057c16f6231b94
Timestamp: 1676927038 Timestamp [UCT]: 2023-02-20 21:03:58 Age [y:d:h:m:s]: 02:257:17:50:37
Block: 701337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 703518 RingCT/type: yes/0
Extra: 01a54b9fd9d876991c6e79d0cb3461147610d44f32fbecc4539e057c16f6231b9402110000000174b6d784000000000000000000

1 output(s) for total of 2.911919009000 dcy

stealth address amount amount idx
00: e23e2e0d48f73cd940fcfd9d9b9aa24473b89f30c8fc187bbeff0f82ef93051e 2.911919009000 1144814 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": 701347, "vin": [ { "gen": { "height": 701337 } } ], "vout": [ { "amount": 2911919009, "target": { "key": "e23e2e0d48f73cd940fcfd9d9b9aa24473b89f30c8fc187bbeff0f82ef93051e" } } ], "extra": [ 1, 165, 75, 159, 217, 216, 118, 153, 28, 110, 121, 208, 203, 52, 97, 20, 118, 16, 212, 79, 50, 251, 236, 196, 83, 158, 5, 124, 22, 246, 35, 27, 148, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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