Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a56e2860a876bf8993bebfadf24fdad0d4cd93b58c58bc32424a582a64fcde16

Tx prefix hash: f615686a3699a28dca8bd6cf1e6d6704b306ec79a5a1324e32b43c32a6b0cfbf
Tx public key: c10b9d307d9138adf140f92ffbe4ea56ccbc7f91f7c843e51d06508310920ff4
Timestamp: 1750508617 Timestamp [UCT]: 2025-06-21 12:23:37 Age [y:d:h:m:s]: 00:159:20:07:03
Block: 1309745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112101 RingCT/type: yes/0
Extra: 01c10b9d307d9138adf140f92ffbe4ea56ccbc7f91f7c843e51d06508310920ff40211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fd515b82faabc68adb6fd7a1d4be10ba308f703c1d7cb800d247f5421cab257 0.600000000000 1797362 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": 1309755, "vin": [ { "gen": { "height": 1309745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fd515b82faabc68adb6fd7a1d4be10ba308f703c1d7cb800d247f5421cab257" } } ], "extra": [ 1, 193, 11, 157, 48, 125, 145, 56, 173, 241, 64, 249, 47, 251, 228, 234, 86, 204, 188, 127, 145, 247, 200, 67, 229, 29, 6, 80, 131, 16, 146, 15, 244, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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