Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb514dae8bac95ebf8f4c335727652bbe0a3305a17cd98b80d22b316fb42c133

Tx prefix hash: c178f8f89cf494a3090b27cd2a8bdf1da6d5d351bce3a130184446ef6c745806
Tx public key: 89ce8f9ed52d81d3405b3890919f3f5b45bdcafbd6cfc0168b9e1043c3b44fff
Timestamp: 1730073667 Timestamp [UCT]: 2024-10-28 00:01:07 Age [y:d:h:m:s]: 00:231:17:28:49
Block: 1141008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165380 RingCT/type: yes/0
Extra: 0189ce8f9ed52d81d3405b3890919f3f5b45bdcafbd6cfc0168b9e1043c3b44fff021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38890f0c4e0f07698136df3e0090926a779143820a897be98a23d664dc1c4abd 0.600000000000 1624815 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": 1141018, "vin": [ { "gen": { "height": 1141008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38890f0c4e0f07698136df3e0090926a779143820a897be98a23d664dc1c4abd" } } ], "extra": [ 1, 137, 206, 143, 158, 213, 45, 129, 211, 64, 91, 56, 144, 145, 159, 63, 91, 69, 189, 202, 251, 214, 207, 192, 22, 139, 158, 16, 67, 195, 180, 79, 255, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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