Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66b11209e5e0fb7ae7958302d134cdbefcb316d73055e9d6d82cef72dd4d88a0

Tx prefix hash: 22e4765ff3e86325e65442b7800d5fca3c42e2803007c61ad768c4c3ae8d74cc
Tx public key: 092cde7a410fd01f541f8fd2aedfc2ac10a8d01228e3423b8a4f06c25889125b
Timestamp: 1647429496 Timestamp [UCT]: 2022-03-16 11:18:16 Age [y:d:h:m:s]: 02:282:14:00:48
Block: 459635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 721505 RingCT/type: yes/0
Extra: 01092cde7a410fd01f541f8fd2aedfc2ac10a8d01228e3423b8a4f06c25889125b021100000015d3fcec30000000000000000000

1 output(s) for total of 18.409360659000 dcy

stealth address amount amount idx
00: 348e9e1dfff2c0ce42f9f2d204219894f2aded79290ead86a491ba6c24381809 18.409360659000 876426 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": 459645, "vin": [ { "gen": { "height": 459635 } } ], "vout": [ { "amount": 18409360659, "target": { "key": "348e9e1dfff2c0ce42f9f2d204219894f2aded79290ead86a491ba6c24381809" } } ], "extra": [ 1, 9, 44, 222, 122, 65, 15, 208, 31, 84, 31, 143, 210, 174, 223, 194, 172, 16, 168, 208, 18, 40, 227, 66, 59, 138, 79, 6, 194, 88, 137, 18, 91, 2, 17, 0, 0, 0, 21, 211, 252, 236, 48, 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