← previous blocknext block →recent activity
Analyzing
Block #91,973,656
30 transactions · 24 stateful · 2026-07-31 17:18:25 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,973,656 · 30 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
1w02w010w012w113w214w315w019w320w121w423w224w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7c4db97…948e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x12595f02…9060
0x065c9d…c394
5 touches
3 conflicts
0x31616f97…1acc
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xa7c4db979d…55948e
Audit this contract →
← previous block·next block →recent activity