← previous blocknext block →recent activity
Analyzing
Block #91,254,087
13 transactions · 12 stateful · 2026-07-29 04:56:13 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,254,087 · 13 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
2w03w14w06w18w29w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbe6a366…8ca1
0x34b655…2a6f
8 touches
6 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
4 touches
1 conflict
0x27034002…2f27
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51197fc5…26c4
0x34b655…2a6f
4 touches
1 conflict
0x571aa8b4…35fa
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 0xfbe6a36638…508ca1
Audit this contract →
← previous block·next block →recent activity