← previous blocknext block →recent activity
Analyzing
Block #91,971,487
25 transactions · 24 stateful · 2026-07-31 17:07:31 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
1.12
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,971,487 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w18w29w310w211w412w314w416w117w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4caa7900…fd2e
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x2f03ebb6…ce4c
0xd32edf…ff58
9 touches
10 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 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: Perpl
10 conflicts on slot 0x4caa7900fe…0ffd2e
Audit this contract →
← previous block·next block →recent activity