Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcd2abacaca621728d2a93cf4690b56c6d902640fa57e4a25968b26b0b0c88db

Tx prefix hash: 2ecc698c3fc5ee6a11d6c0abb07913aa097c44cb7743b3daf34339e1543a18f4
Tx public key: a45f86340c72e5e892ca249db4b50a320bca1f51d89858a3fb8d58bea8fe031d
Timestamp: 1694928430 Timestamp [UCT]: 2023-09-17 05:27:10 Age [y:d:h:m:s]: 01:161:04:04:40
Block: 849884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376243 RingCT/type: yes/0
Extra: 01a45f86340c72e5e892ca249db4b50a320bca1f51d89858a3fb8d58bea8fe031d021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.937522202000 dcy

stealth address amount amount idx
00: 219c387d4640d194406c4f8c4662d8040cfb56b0c414fff16f06a47327c9ad1e 0.937522202000 1303572 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": 849894, "vin": [ { "gen": { "height": 849884 } } ], "vout": [ { "amount": 937522202, "target": { "key": "219c387d4640d194406c4f8c4662d8040cfb56b0c414fff16f06a47327c9ad1e" } } ], "extra": [ 1, 164, 95, 134, 52, 12, 114, 229, 232, 146, 202, 36, 157, 180, 181, 10, 50, 11, 202, 31, 81, 216, 152, 88, 163, 251, 141, 88, 190, 168, 254, 3, 29, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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