← previous blocknext block →recent activity
Analyzing
Block #94,132,975
16 transactions · 14 stateful · 2026-08-08 06:21:23 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,132,975 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc351d6d…256b
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xbf97f631…f804
0x065c9d…c394
3 touches
1 conflict
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x20120943…61ad
0x34b655…2a6f
2 touches
0 conflicts
0x465ef31f…1ed7
0x34b655…2a6f
2 touches
0 conflicts
0x4f647bcf…b0cd
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
3 conflicts on slot 0xcc351d6dd2…b1256b
Audit this contract →
← previous block·next block →recent activity