Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2ad5ae89c8af9d23fd44931d8fea4c75ee0f3e860fd49ef97e1bb88c98bea69

Tx prefix hash: f0e968d7aecc8e9a75981d3d3161deedef78b637783312cdfa8596eb0ca4e7f9
Tx public key: 5b6ccd5069648f7ad756440962f3b2cb8368de25cc4e0d78093d6931cf1e5425
Timestamp: 1736414059 Timestamp [UCT]: 2025-01-09 09:14:19 Age [y:d:h:m:s]: 00:342:04:37:26
Block: 1193498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242110 RingCT/type: yes/0
Extra: 015b6ccd5069648f7ad756440962f3b2cb8368de25cc4e0d78093d6931cf1e54250211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3daa1b03b4a83bae98890ea2500b5b20b8581def366426daa5795af91d8af76d 0.600000000000 1680059 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": 1193508, "vin": [ { "gen": { "height": 1193498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3daa1b03b4a83bae98890ea2500b5b20b8581def366426daa5795af91d8af76d" } } ], "extra": [ 1, 91, 108, 205, 80, 105, 100, 143, 122, 215, 86, 68, 9, 98, 243, 178, 203, 131, 104, 222, 37, 204, 78, 13, 120, 9, 61, 105, 49, 207, 30, 84, 37, 2, 17, 0, 0, 0, 9, 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