← previous blocknext block →recent activity
Analyzing
Block #93,399,166
15 transactions · 15 stateful · 2026-08-05 16:50:40 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,399,166 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w38w410w011w112w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e76cf03…9cc3
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x20492d53…80f9
0x34b655…2a6f
4 touches
1 conflict
0x8fe37a3f…4c89
0x34b655…2a6f
4 touches
1 conflict
0x92511680…9cc0
0x34b655…2a6f
4 touches
1 conflict
0xa8b8fbde…396d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0x5e76cf0367…8a9cc3
Audit this contract →
← previous block·next block →recent activity