← previous blocknext block →recent activity
Analyzing
Block #94,850,257
19 transactions · 19 stateful · 2026-08-10 18:45:51 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,850,257 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w110w111w214w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5767fdec…d9d4
0x34b655…2a6f
6 touches
3 conflicts
0x217dce8d…7e14
0x34b655…2a6f
6 touches
3 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x570bb566…0f21
0x34b655…2a6f
4 touches
1 conflict
0x5bd6c744…92c6
0x34b655…2a6f
4 touches
1 conflict
0x7b67f6cf…0aab
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 0x5767fdeca9…38d9d4
Audit this contract →
← previous block·next block →recent activity