← previous blocknext block →recent activity
Analyzing
Block #94,981,315
7 transactions · 6 stateful · 2026-08-11 05:44:59 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,981,315 · 7 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10f18761…8e0c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd7d3cccb…fd18
0x34b655…2a6f
4 touches
1 conflict
0x01dada3b…0aa7
0x34b655…2a6f
2 touches
0 conflicts
0x01dada3b…0aa8
0x34b655…2a6f
2 touches
0 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
2 touches
0 conflicts
0x320701d5…f9f3
0x34b655…2a6f
2 touches
0 conflicts
0x320701d5…f9f4
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
1 conflict on slot 0x10f187616c…2c8e0c
Audit this contract →
← previous block·next block →recent activity