Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b84669b3336cbe378c68dd4e9339d7520000b2b4dca3a350827ca82273abe2ee

Tx prefix hash: eb9c19ac27636de1ce9550ff6abcb26c89a9cc2137efead307da54e266c9100b
Tx public key: d6a0a947b2e52883fd8109de18a1645ab1668d23f8cc22fbb90f8eb37452f2e2
Timestamp: 1708202082 Timestamp [UCT]: 2024-02-17 20:34:42 Age [y:d:h:m:s]: 00:354:02:06:50
Block: 959743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253191 RingCT/type: yes/0
Extra: 01d6a0a947b2e52883fd8109de18a1645ab1668d23f8cc22fbb90f8eb37452f2e202110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7a9e24e072bc062f503ac447e28869ae3fac201f58b214f22072e9f05e11de7 0.600000000000 1419296 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": 959753, "vin": [ { "gen": { "height": 959743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7a9e24e072bc062f503ac447e28869ae3fac201f58b214f22072e9f05e11de7" } } ], "extra": [ 1, 214, 160, 169, 71, 178, 229, 40, 131, 253, 129, 9, 222, 24, 161, 100, 90, 177, 102, 141, 35, 248, 204, 34, 251, 185, 15, 142, 179, 116, 82, 242, 226, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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