← previous blocknext block →recent activity
Analyzing
Block #91,250,956
17 transactions · 12 stateful · 2026-07-29 04:40:28 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,250,956 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w010w012w113w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50afedcd…91cc
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x930edb63…6ad5
0x065c9d…c394
3 touches
1 conflict
0x1ad2a5a5…6575
0x065c9d…c394
3 touches
1 conflict
0xb9eb1318…ce53
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
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 0x50afedcd15…9a91cc
Audit this contract →
← previous block·next block →recent activity