← previous blocknext block →recent activity
Analyzing
Block #91,423,626
18 transactions · 16 stateful · 2026-07-29 19:10:31 UTC
Parallelism
61/100
Blocked
44%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,423,626 · 18 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
4w06w110w011w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
14 touches
21 conflicts
0x00000000…004c
0x80c745…7210
14 touches
21 conflicts
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x29418a3d…8c6e
0x34b655…2a6f
2 touches
0 conflicts
0x41469894…598f
0x34b655…2a6f
2 touches
0 conflicts
0x41469894…5990
0x34b655…2a6f
2 touches
0 conflicts
0x528d384f…663d
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: 0x80c74517…647210
21 conflicts on slot 0x0000000000…00004b
Audit this contract →
← previous block·next block →recent activity