← previous blocknext block →recent activity
Analyzing
Block #91,425,202
18 transactions · 17 stateful · 2026-07-29 19:19:14 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,425,202 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w18w09w210w312w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x542ff3d0…3fa7
0x34b655…2a6f
8 touches
6 conflicts
0x40ee7a94…d6a8
0x34b655…2a6f
8 touches
6 conflicts
0x84d6407e…6fb2
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641e
0x34b655…2a6f
8 touches
6 conflicts
0xe48c4dad…9175
0x34b655…2a6f
8 touches
6 conflicts
0x4abfb389…18f4
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x542ff3d046…773fa7
Audit this contract →
← previous block·next block →recent activity