← previous blocknext block →recent activity
Analyzing
Block #91,253,019
16 transactions · 15 stateful · 2026-07-29 04:50:51 UTC
Parallelism
50/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,253,019 · 16 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
2w03w15w26w07w110w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x347e7e76…914b
0x34b655…2a6f
8 touches
6 conflicts
0x4943c7e5…d013
0x34b655…2a6f
8 touches
6 conflicts
0x3c5fae50…a4bb
0x34b655…2a6f
8 touches
6 conflicts
0xc7139ac0…16c6
0x34b655…2a6f
8 touches
6 conflicts
0x05d353a8…5168
0x34b655…2a6f
6 touches
3 conflicts
0x1426ef74…28c4
0x34b655…2a6f
6 touches
3 conflicts
0x21ed3831…61e5
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity