Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 165e5d980699b544f33bd4668366ae723f34530e9ddcf21041d0a11325444e3e

Tx prefix hash: 26188616885208e0f1fb95f9814be95256e105054aa8a827f8de32b46a593c2f
Tx public key: be72f33c6b1f523fdc1e8181c415b4591052ed2709d130c226aafe75642f214f
Timestamp: 1721524614 Timestamp [UCT]: 2024-07-21 01:16:54 Age [y:d:h:m:s]: 00:247:18:50:44
Block: 1070199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176990 RingCT/type: yes/0
Extra: 01be72f33c6b1f523fdc1e8181c415b4591052ed2709d130c226aafe75642f214f0211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e75fd85cb4bb8d5ef508d0ee0c57a2080a4b58edb65d39c1af62884b49b8dfc6 0.600000000000 1541932 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": 1070209, "vin": [ { "gen": { "height": 1070199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e75fd85cb4bb8d5ef508d0ee0c57a2080a4b58edb65d39c1af62884b49b8dfc6" } } ], "extra": [ 1, 190, 114, 243, 60, 107, 31, 82, 63, 220, 30, 129, 129, 196, 21, 180, 89, 16, 82, 237, 39, 9, 209, 48, 194, 38, 170, 254, 117, 100, 47, 33, 79, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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