Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ba9a3f3f3cf50e6befe363339c310d5b9351c0d379e069ef37c455de6ac1d6a

Tx prefix hash: ca9931d87f8741c5c70afde85afce19fce83917fef36d0824b881c1eca530289
Tx public key: b954a87cb85d774ea9f42cb9879babe884fb1dd5d2feafc3568e3ba414847afa
Timestamp: 1710314521 Timestamp [UCT]: 2024-03-13 07:22:01 Age [y:d:h:m:s]: 00:246:02:22:05
Block: 977265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176179 RingCT/type: yes/0
Extra: 01b954a87cb85d774ea9f42cb9879babe884fb1dd5d2feafc3568e3ba414847afa02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6a671152e03c4c88f89b34a77ae8750c692fbf33fb8b25f1d1ad59112d72083 0.600000000000 1437266 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": 977275, "vin": [ { "gen": { "height": 977265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6a671152e03c4c88f89b34a77ae8750c692fbf33fb8b25f1d1ad59112d72083" } } ], "extra": [ 1, 185, 84, 168, 124, 184, 93, 119, 78, 169, 244, 44, 185, 135, 155, 171, 232, 132, 251, 29, 213, 210, 254, 175, 195, 86, 142, 59, 164, 20, 132, 122, 250, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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