Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f2e44052b757c8cf5898b1968693bc7beb7cf3248ba293c01552d8476302a0c

Tx prefix hash: 1fe540f3577dafefb8ed3c1378def964556ee399740f907dd32587d0279c0020
Tx public key: d03f99857a9fc9cde6c2e793df12d0eecdf724df20071a2843b8f4a08a273313
Timestamp: 1696680424 Timestamp [UCT]: 2023-10-07 12:07:04 Age [y:d:h:m:s]: 01:143:20:53:55
Block: 864423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363842 RingCT/type: yes/0
Extra: 01d03f99857a9fc9cde6c2e793df12d0eecdf724df20071a2843b8f4a08a273313021100000006faf35c9c000000000000000000

1 output(s) for total of 0.839088555000 dcy

stealth address amount amount idx
00: 7cdef768dec748936630b967132d235131f81bd5d93a4025981bd8c86152a891 0.839088555000 1318937 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": 864433, "vin": [ { "gen": { "height": 864423 } } ], "vout": [ { "amount": 839088555, "target": { "key": "7cdef768dec748936630b967132d235131f81bd5d93a4025981bd8c86152a891" } } ], "extra": [ 1, 208, 63, 153, 133, 122, 159, 201, 205, 230, 194, 231, 147, 223, 18, 208, 238, 205, 247, 36, 223, 32, 7, 26, 40, 67, 184, 244, 160, 138, 39, 51, 19, 2, 17, 0, 0, 0, 6, 250, 243, 92, 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