← previous blocknext block →recent activity
Analyzing
Block #91,798,655
25 transactions · 20 stateful · 2026-07-31 02:38:00 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,798,655 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w29w310w413w014w515w117w619w420w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54df317e…b739
0x34b655…2a6f
10 touches
10 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
10 touches
10 conflicts
0xfd42a6b9…4c81
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x774b87ba…3f2c
0x34b655…2a6f
6 touches
3 conflicts
0xa5811d93…8c73
0x34b655…2a6f
6 touches
3 conflicts
0xb6fcbbb7…2b31
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 0x54df317ed4…1ab739
Audit this contract →
← previous block·next block →recent activity