Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a140c7158ac06c2b05628d3778919a1a2b6df1003dc064d0258be46be9b23858

Tx prefix hash: c9f0da1d09c7c6a2e3429564e5f182111fbf891ea7fcd5a15fa0d7137d75eb0b
Tx public key: 55f3dc2a9e2a97ab97814f581ac303503d8f7e09f3b9f988a2ef88ddd9acb43c
Timestamp: 1712512346 Timestamp [UCT]: 2024-04-07 17:52:26 Age [y:d:h:m:s]: 01:002:04:37:41
Block: 995446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262549 RingCT/type: yes/0
Extra: 0155f3dc2a9e2a97ab97814f581ac303503d8f7e09f3b9f988a2ef88ddd9acb43c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bf851d3bec113d6e66170c5dd8cdbefa68d28107408b884f5c5e9a12ffa73af 0.600000000000 1455854 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": 995456, "vin": [ { "gen": { "height": 995446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bf851d3bec113d6e66170c5dd8cdbefa68d28107408b884f5c5e9a12ffa73af" } } ], "extra": [ 1, 85, 243, 220, 42, 158, 42, 151, 171, 151, 129, 79, 88, 26, 195, 3, 80, 61, 143, 126, 9, 243, 185, 249, 136, 162, 239, 136, 221, 217, 172, 180, 60, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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