← previous blocknext block →recent activity
Analyzing
Block #91,763,120
20 transactions · 14 stateful · 2026-07-30 23:39:15 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,763,120 · 20 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
1w03w17w08w110w111w216w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x265a95d7…d10a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x95d63682…276c
0x34b655…2a6f
6 touches
3 conflicts
0x5e4a27a0…ffce
0x34b655…2a6f
6 touches
3 conflicts
0xcc58c80b…ff79
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 conflicts
0xf2e22c06…42d6
0x34b655…2a6f
6 touches
3 conflicts
0x5cd498ab…27cf
0x065c9d…c394
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 0x265a95d7f6…0dd10a
Audit this contract →
← previous block·next block →recent activity