Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6a1fb2fa0f74525f2711c070b8243ca2488e0fe8d94bc550a2f334f85c1e469

Tx prefix hash: cbf12b9ea7ba0ed69be34d0c42143dffab064ac416e619d23522ba1270bd4e5c
Tx public key: 444aa2be044fe5109055aeaccb95d7eeef67e46e62ab5424eca0dafd730b2109
Timestamp: 1639377455 Timestamp [UCT]: 2021-12-13 06:37:35 Age [y:d:h:m:s]: 03:151:09:14:33
Block: 394440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 886961 RingCT/type: yes/0
Extra: 01444aa2be044fe5109055aeaccb95d7eeef67e46e62ab5424eca0dafd730b21090211000000020eb261b4000000000000000000

1 output(s) for total of 30.273100296000 dcy

stealth address amount amount idx
00: 121be9e2541ffc8e57d6576a2a48b122d3929f38353dc96ea758b3871c5102ad 30.273100296000 792031 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": 394450, "vin": [ { "gen": { "height": 394440 } } ], "vout": [ { "amount": 30273100296, "target": { "key": "121be9e2541ffc8e57d6576a2a48b122d3929f38353dc96ea758b3871c5102ad" } } ], "extra": [ 1, 68, 74, 162, 190, 4, 79, 229, 16, 144, 85, 174, 172, 203, 149, 215, 238, 239, 103, 228, 110, 98, 171, 84, 36, 236, 160, 218, 253, 115, 11, 33, 9, 2, 17, 0, 0, 0, 2, 14, 178, 97, 180, 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