Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43a626d617d630f077694a9e22e8ebd985f3ad5b97506a1d16fcea3838111e86

Tx prefix hash: 4835dfdf7a578c5f9b905d54d6c52ae171db2bb12e207d6ea2a3ddc3c7805758
Tx public key: d4b4c80a6da1e6902a492f97af943fe8c5833625c57a8d8e25d2da50fc24b3e9
Timestamp: 1724093844 Timestamp [UCT]: 2024-08-19 18:57:24 Age [y:d:h:m:s]: 00:228:20:14:17
Block: 1091503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163416 RingCT/type: yes/0
Extra: 01d4b4c80a6da1e6902a492f97af943fe8c5833625c57a8d8e25d2da50fc24b3e902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61cc7534a072a5dedecec248daf3da0bdeb138f95f1e657a0b4b07f3e0fb54a4 0.600000000000 1566136 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": 1091513, "vin": [ { "gen": { "height": 1091503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61cc7534a072a5dedecec248daf3da0bdeb138f95f1e657a0b4b07f3e0fb54a4" } } ], "extra": [ 1, 212, 180, 200, 10, 109, 161, 230, 144, 42, 73, 47, 151, 175, 148, 63, 232, 197, 131, 54, 37, 197, 122, 141, 142, 37, 210, 218, 80, 252, 36, 179, 233, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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