← previous blocknext block →recent activity
Analyzing
Block #91,249,217
33 transactions · 31 stateful · 2026-07-29 04:31:43 UTC
Parallelism
70/100
Blocked
58%
Avg conflicts / tx
1.52
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,249,217 · 33 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
3w04w16w07w18w09w110w211w312w415w017w118w119w420w222w323w425w526w627w728w829w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xb56f0740…7542
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
8 touches
6 conflicts
0x539ac47f…eb6f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x86aa0fcf…dc05
0x34b655…2a6f
6 touches
3 conflicts
0xb10efc7d…60f4
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity