← previous blocknext block →recent activity
Analyzing
Block #92,973,723
6 transactions · 5 stateful · 2026-08-04 05:09:50 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,973,723 · 6 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2dea5397…7e8c
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x6e247eb5…7708
0x34b655…2a6f
3 touches
1 conflict
0x2311a0fd…47d6
0x34b655…2a6f
3 touches
1 conflict
0x1d6cb721…c88c
0x34b655…2a6f
2 touches
0 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
2 touches
0 conflicts
0x3bdcb446…47dc
0x34b655…2a6f
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 0x2dea5397e4…9b7e8c
Audit this contract →
← previous block·next block →recent activity