← previous blocknext block →recent activity
Analyzing
Block #91,257,054
15 transactions · 13 stateful · 2026-07-29 05:11:11 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,257,054 · 15 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
1w02w14w25w36w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x1b80cf69…7439
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x26851c5a…c02b
0x34b655…2a6f
4 touches
1 conflict
0x2bbc37af…2efe
0x34b655…2a6f
4 touches
1 conflict
0x381c126b…20f9
0x34b655…2a6f
4 touches
1 conflict
0x446e4f62…f7b6
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity