← previous blocknext block →recent activity
Analyzing
Block #94,813,466
27 transactions · 24 stateful · 2026-08-10 15:40:44 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
1.48
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #94,813,466 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w39w410w513w416w620w221w324w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
14 touches
21 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x3cb4b659…f735
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity