← previous blocknext block →recent activity
Analyzing
Block #94,856,569
11 transactions · 8 stateful · 2026-08-10 19:17:35 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,856,569 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07d8b1e8…78c6
0x34b655…2a6f
6 touches
3 conflicts
0xbb0145cf…5450
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x007c19a0…3af4
0x34b655…2a6f
2 touches
0 conflicts
0x1176d678…20ef
0x34b655…2a6f
2 touches
0 conflicts
0x24b08f9c…e594
0x34b655…2a6f
2 touches
0 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
2 touches
0 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
2 touches
0 conflicts
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 0x07d8b1e8f0…0978c6
Audit this contract →
← previous block·next block →recent activity