← previous blocknext block →recent activity
Analyzing
Block #91,071,905
19 transactions · 17 stateful · 2026-07-28 13:39:36 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,071,905 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w27w09w111w312w215w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3841818b…e1e7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x1bd5f660…87df
0x40c49f…2af0
5 touches
3 conflicts
0xbaa024a6…0f11
0x40c49f…2af0
4 touches
1 conflict
0xffa7d0a4…b10a
0x40c49f…2af0
4 touches
1 conflict
0x864d5f27…5fe3
0x40c49f…2af0
4 touches
1 conflict
0x3c0e49c9…7833
0x34b655…2a6f
4 touches
1 conflict
0x3e3f27ce…580c
0x34b655…2a6f
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
3 conflicts on slot 0x3841818bc2…dbe1e7
Audit this contract →
← previous block·next block →recent activity