← previous blocknext block →recent activity
Analyzing
Block #91,075,008
23 transactions · 18 stateful · 2026-07-28 13:55:13 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,075,008 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w18w09w110w011w113w219w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35a9f06c…7689
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49ffd065…33d1
0x34b655…2a6f
4 touches
1 conflict
0x5bc6b706…fce6
0x34b655…2a6f
4 touches
1 conflict
0x61e273d4…7a19
0x34b655…2a6f
4 touches
1 conflict
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0x79e8f935…c3b6
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
3 conflicts on slot 0x35a9f06ccf…e37689
Audit this contract →
← previous block·next block →recent activity