← previous blocknext block →recent activity
Analyzing
Block #91,076,137
29 transactions · 25 stateful · 2026-07-28 14:00:55 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,076,137 · 29 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
1w02w04w07w08w112w213w314w115w116w117w218w020w121w222w324w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92115abd…ad76
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x3464bbc5…a323
0xa6afd3…d132
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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 0x92115abda4…1fad76
Audit this contract →
← previous block·next block →recent activity