← previous blocknext block →recent activity
Analyzing
Block #94,684,872
21 transactions · 21 stateful · 2026-08-10 04:52:27 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,684,872 · 21 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
2w05w16w27w38w313w014w115w218w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc351d6d…256b
0x34b655…2a6f
8 touches
6 conflicts
0x4633fac1…c113
0x34b655…2a6f
6 touches
3 conflicts
0x10142c6e…5822
0x34b655…2a6f
6 touches
3 conflicts
0xdf4f5752…f6e6
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
6 conflicts on slot 0xcc351d6dd2…b1256b
Audit this contract →
← previous block·next block →recent activity