Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b435055cbe5a49bfbf48c819f7a1d6f0470ce8f8195a1d56494318133041c27

Tx prefix hash: 6ff0b54543e9999e5d0dd36bdfc7ee122f9fc2a101694951f948e73ed9c7f062
Tx public key: 065ee23ceee3efadb842ce2f5bb637d518c2ca342421af4bb6c7e867f6b9918c
Timestamp: 1764284580 Timestamp [UCT]: 2025-11-27 23:03:00 Age [y:d:h:m:s]: 00:026:00:41:22
Block: 1421579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18606 RingCT/type: yes/0
Extra: 01065ee23ceee3efadb842ce2f5bb637d518c2ca342421af4bb6c7e867f6b9918c0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4234ad5843b0d87eaa06d1c964771a43aac8f8e8efea39d071cde6b6d51274a 0.600000000000 1910136 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": 1421589, "vin": [ { "gen": { "height": 1421579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4234ad5843b0d87eaa06d1c964771a43aac8f8e8efea39d071cde6b6d51274a" } } ], "extra": [ 1, 6, 94, 226, 60, 238, 227, 239, 173, 184, 66, 206, 47, 91, 182, 55, 213, 24, 194, 202, 52, 36, 33, 175, 75, 182, 199, 232, 103, 246, 185, 145, 140, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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