← previous blocknext block →recent activity
Analyzing
Block #91,403,645
10 transactions · 8 stateful · 2026-07-29 17:29:41 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,403,645 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc66586e…20fe
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xd23dd381…0a78
0x34b655…2a6f
4 touches
1 conflict
0x3bdd71a2…b6eb
0x34b655…2a6f
2 touches
0 conflicts
0x548145a9…cfce
0x34b655…2a6f
2 touches
0 conflicts
0x6ac511de…23d8
0x34b655…2a6f
2 touches
0 conflicts
0x8e507257…71c1
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xbc66586e8f…a220fe
Audit this contract →
← previous block·next block →recent activity