Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5627eb8b6e6dd18fdcbc309d6c541de10c3e6cde0b262bfea53defb23efdefa3

Tx prefix hash: 1b2849e8116cc7f0390fdd1d98da11eea2c24f0430708a1bbc2cefe0a34dff94
Tx public key: 66e648b47c754a2aa9656823a03741579a80dbbb78a22b36f034e2b696eced01
Timestamp: 1763400821 Timestamp [UCT]: 2025-11-17 17:33:41 Age [y:d:h:m:s]: 00:050:17:06:45
Block: 1414236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36318 RingCT/type: yes/0
Extra: 0166e648b47c754a2aa9656823a03741579a80dbbb78a22b36f034e2b696eced0102110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aeb42273dd029dc88a2b9cb293751dafcf5aef1a411a13eb2c9979e66cad4f7f 0.600000000000 1902723 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": 1414246, "vin": [ { "gen": { "height": 1414236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aeb42273dd029dc88a2b9cb293751dafcf5aef1a411a13eb2c9979e66cad4f7f" } } ], "extra": [ 1, 102, 230, 72, 180, 124, 117, 74, 42, 169, 101, 104, 35, 160, 55, 65, 87, 154, 128, 219, 187, 120, 162, 43, 54, 240, 52, 226, 182, 150, 236, 237, 1, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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