← previous blocknext block →recent activity
Analyzing
Block #94,201,363
13 transactions · 11 stateful · 2026-08-08 12:07:57 UTC
Parallelism
62/100
Blocked
64%
Avg conflicts / tx
1.15
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,201,363 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w16w07w38w49w411w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
6 touches
3 conflicts
0x3c5d903c…aa03
0x34b655…2a6f
6 touches
3 conflicts
0x8c8774b6…40b9
0x34b655…2a6f
6 touches
3 conflicts
0xabcf581f…731a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…7215
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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
6 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity