Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d43edfe34ae82c24d2a95c187d03f861efd3fc04e84ec54bde26240f5b82697

Tx prefix hash: 1e897993cf2285c2fe9aabb0be97ce8d5e82e87e45efeb89fbf458e9722f8673
Tx public key: 8f085a5614ac31f2a06ce1c228a46773e4ea49f22363153aa65f669703b5839f
Timestamp: 1706946138 Timestamp [UCT]: 2024-02-03 07:42:18 Age [y:d:h:m:s]: 01:276:04:02:59
Block: 949317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456153 RingCT/type: yes/0
Extra: 018f085a5614ac31f2a06ce1c228a46773e4ea49f22363153aa65f669703b5839f0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64ffac28f1bda224166880f52e21a2c319ff7ebef061a58064c6ddc10cc97e61 0.600000000000 1407841 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": 949327, "vin": [ { "gen": { "height": 949317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64ffac28f1bda224166880f52e21a2c319ff7ebef061a58064c6ddc10cc97e61" } } ], "extra": [ 1, 143, 8, 90, 86, 20, 172, 49, 242, 160, 108, 225, 194, 40, 164, 103, 115, 228, 234, 73, 242, 35, 99, 21, 58, 166, 95, 102, 151, 3, 181, 131, 159, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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