Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d128ee3ead718c41e8f36794eed24b884e1dc81a8c8eb5d859ee75b9a012e37

Tx prefix hash: fcf628ca1adfb6a99038b61ab081a969570101b51166a41fb6c862accb5b938a
Tx public key: 4bea04dd56680e3b9e8d3264bcd4725dcd96b6a93787b82df318d1243227a92e
Timestamp: 1759828604 Timestamp [UCT]: 2025-10-07 09:16:44 Age [y:d:h:m:s]: 00:033:15:09:51
Block: 1384633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24087 RingCT/type: yes/0
Extra: 014bea04dd56680e3b9e8d3264bcd4725dcd96b6a93787b82df318d1243227a92e021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3b0019059f531a4f228cd76c8418c026350e03eae119e38341404c7885d1104 0.600000000000 1872786 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": 1384643, "vin": [ { "gen": { "height": 1384633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3b0019059f531a4f228cd76c8418c026350e03eae119e38341404c7885d1104" } } ], "extra": [ 1, 75, 234, 4, 221, 86, 104, 14, 59, 158, 141, 50, 100, 188, 212, 114, 93, 205, 150, 182, 169, 55, 135, 184, 45, 243, 24, 209, 36, 50, 39, 169, 46, 2, 17, 0, 0, 0, 2, 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