← previous blocknext block →recent activity
Analyzing
Block #94,668,676
11 transactions · 8 stateful · 2026-08-10 03:30:58 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,668,676 · 11 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
2w04w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50afedcd…91cc
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x9d6946b4…7f4e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xab9af436…a93d
0x34b655…2a6f
3 touches
1 conflict
0xf46ac1c9…8158
0x34b655…2a6f
3 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
2 touches
0 conflicts
0x2c41323b…0d36
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 0x50afedcd15…9a91cc
Audit this contract →
← previous block·next block →recent activity