Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 565da8d748786de558469fc095136d6fe1a26e330c347ffe42cdac0452c5e9ca

Tx prefix hash: 28855b0833f32ae8392fdaaa9a609210e24c127655f2a398af24a34e6d91596b
Tx public key: d0b0d4323dbfe5a07761d15b49e0e1f0e157a8e4e93b56517e2620d00a988670
Timestamp: 1728127380 Timestamp [UCT]: 2024-10-05 11:23:00 Age [y:d:h:m:s]: 00:180:09:46:27
Block: 1124936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128726 RingCT/type: yes/0
Extra: 01d0b0d4323dbfe5a07761d15b49e0e1f0e157a8e4e93b56517e2620d00a98867002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6f73c9bdf55fcdd749c89d1b3bb718b7e07f43a30cdc48b922ec760ef988469 0.600000000000 1607609 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": 1124946, "vin": [ { "gen": { "height": 1124936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6f73c9bdf55fcdd749c89d1b3bb718b7e07f43a30cdc48b922ec760ef988469" } } ], "extra": [ 1, 208, 176, 212, 50, 61, 191, 229, 160, 119, 97, 209, 91, 73, 224, 225, 240, 225, 87, 168, 228, 233, 59, 86, 81, 126, 38, 32, 208, 10, 152, 134, 112, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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