Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f50cc111861fa618f43c3d524c9a75c5d29c8cbb88f1042c4b99d2f900849b0

Tx prefix hash: e71ba615956f3f891761ae71ba6349ae2b1b34c810f4c0689daa4d26448bf8cc
Tx public key: 8eee8737b03c148051f03912f7399115744503d4733f2406c41c077db7b6ec38
Timestamp: 1761557518 Timestamp [UCT]: 2025-10-27 09:31:58 Age [y:d:h:m:s]: 00:097:01:40:59
Block: 1398978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69309 RingCT/type: yes/0
Extra: 018eee8737b03c148051f03912f7399115744503d4733f2406c41c077db7b6ec38021100000007d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e40750fbab3e24f9ec8f6f26cfcd1960ac78315be6b2c3746d315d26e91fe10 0.600000000000 1887281 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": 1398988, "vin": [ { "gen": { "height": 1398978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e40750fbab3e24f9ec8f6f26cfcd1960ac78315be6b2c3746d315d26e91fe10" } } ], "extra": [ 1, 142, 238, 135, 55, 176, 60, 20, 128, 81, 240, 57, 18, 247, 57, 145, 21, 116, 69, 3, 212, 115, 63, 36, 6, 196, 28, 7, 125, 183, 182, 236, 56, 2, 17, 0, 0, 0, 7, 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