Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89bf9203c5134be4a18a999958df153e581d323b44d9ce613d16b4dbadfb7751

Tx prefix hash: c1c06bf5141b3f09e084f924acdebee315eed6f318dd3dbf2e2ca577e75dd455
Tx public key: af00d6f6829706600db9e5d64cabae42d2971a6310ae87dad59ea86a1c6b68ab
Timestamp: 1752905819 Timestamp [UCT]: 2025-07-19 06:16:59 Age [y:d:h:m:s]: 00:157:18:00:22
Block: 1328642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111573 RingCT/type: yes/0
Extra: 01af00d6f6829706600db9e5d64cabae42d2971a6310ae87dad59ea86a1c6b68ab021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97051073216b3de9a6569dae67a4a3e9b54a520799056f6b0225a669a87d6fed 0.600000000000 1816405 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": 1328652, "vin": [ { "gen": { "height": 1328642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97051073216b3de9a6569dae67a4a3e9b54a520799056f6b0225a669a87d6fed" } } ], "extra": [ 1, 175, 0, 214, 246, 130, 151, 6, 96, 13, 185, 229, 214, 76, 171, 174, 66, 210, 151, 26, 99, 16, 174, 135, 218, 213, 158, 168, 106, 28, 107, 104, 171, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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