← previous blocknext block →recent activity
Analyzing
Block #91,779,872
20 transactions · 15 stateful · 2026-07-31 01:03:31 UTC
Parallelism
90/100
Blocked
27%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,779,872 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w09w012w114w116w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xb566cc65…214d
0xa6afd3…d132
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x1a8293b0…56c7
0x065c9d…c394
2 touches
0 conflicts
0x9cb02baf…d652
0x065c9d…c394
2 touches
0 conflicts
0xf97c5ab6…1581
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
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: Perpl
1 conflict on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity