← previous blocknext block →recent activity
Analyzing
Block #91,406,434
13 transactions · 13 stateful · 2026-07-29 17:43:48 UTC
Parallelism
46/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,406,434 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w47w510w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4b76f967…295f
0x34b655…2a6f
4 touches
1 conflict
0x4ec5ff53…d470
0x34b655…2a6f
4 touches
1 conflict
0x609e537a…511d
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity