Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d1e8002ad7fbeb3531e221ff3e285a039e56c7cd990c0ff675d75e50bdf5616

Tx prefix hash: be5bc4ff3649a4528e6c5094147b61ecc24cf6dd1094caf8313c8b8934c5e848
Tx public key: a8c2da5c2bfb9b105168ae04163eefce597d9703518aa8a9348c48e0ab756d92
Timestamp: 1733317640 Timestamp [UCT]: 2024-12-04 13:07:20 Age [y:d:h:m:s]: 00:121:07:36:32
Block: 1167859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86506 RingCT/type: yes/0
Extra: 01a8c2da5c2bfb9b105168ae04163eefce597d9703518aa8a9348c48e0ab756d920211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a86606aed75f2b7ee9ea8a0fcbd21704a9f7727713f99d7aa53286127cbf8f8e 0.600000000000 1653562 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": 1167869, "vin": [ { "gen": { "height": 1167859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a86606aed75f2b7ee9ea8a0fcbd21704a9f7727713f99d7aa53286127cbf8f8e" } } ], "extra": [ 1, 168, 194, 218, 92, 43, 251, 155, 16, 81, 104, 174, 4, 22, 62, 239, 206, 89, 125, 151, 3, 81, 138, 168, 169, 52, 140, 72, 224, 171, 117, 109, 146, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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