← previous blocknext block →recent activity
Analyzing
Block #91,141,998
18 transactions · 16 stateful · 2026-07-28 19:32:19 UTC
Parallelism
39/100
Blocked
69%
Avg conflicts / tx
2.22
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,141,998 · 18 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w712w813w914w1016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
18 touches
36 conflicts
0xce06a0f7…efef
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0x47a8d7fd…bb90
0x34b655…2a6f
7 touches
6 conflicts
0xe7e43bc4…b9fb
0x34b655…2a6f
6 touches
3 conflicts
0x7be3246e…f89f
0x34b655…2a6f
6 touches
3 conflicts
0x6f816022…0f2d
0x34b655…2a6f
5 touches
3 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
36 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity