Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a7ff8b7888e5e92fe742317e97cbd426dfb5e9b4726bb9008ec66403bdd2c60

Tx prefix hash: 0d37897c91491a6224707704710e2f962a798567969827d9cabd7e1be2ae81e0
Tx public key: 56997603f24b31621deddb3a1e06a9001c0fb279b4551bd504f8cc7e976ada7c
Timestamp: 1711067763 Timestamp [UCT]: 2024-03-22 00:36:03 Age [y:d:h:m:s]: 01:003:15:34:23
Block: 983522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263555 RingCT/type: yes/0
Extra: 0156997603f24b31621deddb3a1e06a9001c0fb279b4551bd504f8cc7e976ada7c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bfaf1f27f3ff4c10ad892165a9196b6b15059c4931b7d4440037e2e51fd03e0 0.600000000000 1443663 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": 983532, "vin": [ { "gen": { "height": 983522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bfaf1f27f3ff4c10ad892165a9196b6b15059c4931b7d4440037e2e51fd03e0" } } ], "extra": [ 1, 86, 153, 118, 3, 242, 75, 49, 98, 29, 237, 219, 58, 30, 6, 169, 0, 28, 15, 178, 121, 180, 85, 27, 213, 4, 248, 204, 126, 151, 106, 218, 124, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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