← previous blocknext block →recent activity
Analyzing
Block #94,200,880
16 transactions · 14 stateful · 2026-08-08 12:05:31 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,200,880 · 16 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
1w02w13w25w36w49w514w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8dfb88f5…5592
0x34b655…2a6f
4 touches
1 conflict
0xbf270684…c6f4
0x34b655…2a6f
4 touches
1 conflict
0x3bab4355…fbfd
0x34b655…2a6f
4 touches
1 conflict
0x4560e5a8…b741
0x34b655…2a6f
4 touches
1 conflict
0xde04b8a1…8db0
0x34b655…2a6f
4 touches
1 conflict
0xeb9129e1…30b0
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
10 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity