← previous blocknext block →recent activity
Analyzing
Block #94,286,156
12 transactions · 9 stateful · 2026-08-08 19:17:41 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,286,156 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd210a3b3…eb4e
0x34b655…2a6f
4 touches
1 conflict
0x1d5181ef…7074
0x34b655…2a6f
4 touches
1 conflict
0x5fdeee5f…f6c3
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xcee176f8…a030
0x34b655…2a6f
4 touches
1 conflict
0xab304d86…6418
0x0a4fcb…a602
2 touches
0 conflicts
0xab304d86…641c
0x0a4fcb…a602
2 touches
0 conflicts
0xab304d86…641d
0x0a4fcb…a602
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
1 conflict on slot 0xd210a3b342…37eb4e
Audit this contract →
← previous block·next block →recent activity