← previous blocknext block →recent activity
Analyzing
Block #92,573,693
9 transactions · 8 stateful · 2026-08-02 19:36:10 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,573,693 · 9 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5666db7d…5dc4
0x34b655…2a6f
4 touches
1 conflict
0x9dd0a735…4d04
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x31b60059…7900
0x2b5cd4…1a0a
2 touches
0 conflicts
0x4ed38792…c984
0x2b5cd4…1a0a
2 touches
0 conflicts
0x52c63247…ce02
0x2b5cd4…1a0a
2 touches
0 conflicts
0x8801fa2e…3edb
0x2b5cd4…1a0a
2 touches
0 conflicts
0x7aa512ae…d2e0
0x754704…b603
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 0x5666db7d94…495dc4
Audit this contract →
← previous block·next block →recent activity