Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 518eae02a97318b4769b5a86cb4cdd041fbdaab97c5260043fe47979c9c10ea7

Tx prefix hash: 81aa6023782076aae47691b642d15b7420526c526ad9dee3a0b394dcb8b62961
Tx public key: a87f3005dcc9106e2f51adf73833c52cb7533934a70c7027eaad35b338c504bd
Timestamp: 1758935230 Timestamp [UCT]: 2025-09-27 01:07:10 Age [y:d:h:m:s]: 00:050:03:19:46
Block: 1377234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35905 RingCT/type: yes/0
Extra: 01a87f3005dcc9106e2f51adf73833c52cb7533934a70c7027eaad35b338c504bd021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e05c4dc3e355bdb75a9066df0b0b6cfc7a6ff52a9b249aed8568dee3fbcf010c 0.600000000000 1865325 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": 1377244, "vin": [ { "gen": { "height": 1377234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e05c4dc3e355bdb75a9066df0b0b6cfc7a6ff52a9b249aed8568dee3fbcf010c" } } ], "extra": [ 1, 168, 127, 48, 5, 220, 201, 16, 110, 47, 81, 173, 247, 56, 51, 197, 44, 183, 83, 57, 52, 167, 12, 112, 39, 234, 173, 53, 179, 56, 197, 4, 189, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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