← previous blocknext block →recent activity
Analyzing
Block #91,288,943
12 transactions · 11 stateful · 2026-07-29 07:52:23 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,288,943 · 12 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
2w03w15w26w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a6b3039…6a98
0x34b655…2a6f
6 touches
3 conflicts
0x32fc0df3…0ed0
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x13306c72…fb14
0x34b655…2a6f
4 touches
1 conflict
0x8ce1ffed…4889
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3e5604c0…8bc3
0x34b655…2a6f
2 touches
0 conflicts
0x3ffb5260…d8fa
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
3 conflicts on slot 0x4a6b3039f4…046a98
Audit this contract →
← previous block·next block →recent activity