← previous blocknext block →recent activity
Analyzing
Block #91,977,653
22 transactions · 22 stateful · 2026-07-31 17:38:32 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,977,653 · 22 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
1w02w14w05w18w09w110w213w314w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x394b760c…3c4c
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xfa324e43…8896
0x1b6862…e19c
4 touches
1 conflict
0x085df2c1…305a
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
3 conflicts on slot 0x394b760c4e…9d3c4c
Audit this contract →
← previous block·next block →recent activity