Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e1f427275de7335040b6e76342126bb79c044b32a860c1020b6a26dd28321e3

Tx prefix hash: d7c265fec3f44ced3699fa402df17c057994c9276d15dc639629a7c447351dba
Tx public key: 09e6ff7b9e6f7bbf14ec7da46a9c0f379be97d699ce19a9deb9bd8894e954a01
Timestamp: 1722989665 Timestamp [UCT]: 2024-08-07 00:14:25 Age [y:d:h:m:s]: 00:169:18:38:13
Block: 1082335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121424 RingCT/type: yes/0
Extra: 0109e6ff7b9e6f7bbf14ec7da46a9c0f379be97d699ce19a9deb9bd8894e954a0102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b117fd7000197c8722ee378838a83cb1e922bcd556aeb738c6bfe329c4b1b0f2 0.600000000000 1556160 of 15

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": 1082345, "vin": [ { "gen": { "height": 1082335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b117fd7000197c8722ee378838a83cb1e922bcd556aeb738c6bfe329c4b1b0f2" } } ], "extra": [ 1, 9, 230, 255, 123, 158, 111, 123, 191, 20, 236, 125, 164, 106, 156, 15, 55, 155, 233, 125, 105, 156, 225, 154, 157, 235, 155, 216, 137, 78, 149, 74, 1, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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