Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eda2ad57dbe1465caaa940bde49241c6a0d15a5e1b49631478617a93c5bb2c9d

Tx prefix hash: 54b76e400996db30243e7a7afbb066555cb22dadbb204574ea685e104601a8b9
Tx public key: 4a35b972d7ae8ff8f12a4397f963110395ea42b3ab609f1f0b66470693f1e030
Timestamp: 1735756787 Timestamp [UCT]: 2025-01-01 18:39:47 Age [y:d:h:m:s]: 00:355:15:59:20
Block: 1188051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251750 RingCT/type: yes/0
Extra: 014a35b972d7ae8ff8f12a4397f963110395ea42b3ab609f1f0b66470693f1e030021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6d500865aac22127ac01158587ec26e7fab9158501a2417a91b3c01ba269e33 0.600000000000 1674550 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": 1188061, "vin": [ { "gen": { "height": 1188051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6d500865aac22127ac01158587ec26e7fab9158501a2417a91b3c01ba269e33" } } ], "extra": [ 1, 74, 53, 185, 114, 215, 174, 143, 248, 241, 42, 67, 151, 249, 99, 17, 3, 149, 234, 66, 179, 171, 96, 159, 31, 11, 102, 71, 6, 147, 241, 224, 48, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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