← previous blocknext block →recent activity
Analyzing
Block #92,297,898
9 transactions · 9 stateful · 2026-08-01 20:29:10 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,297,898 · 9 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
2w03w14w25w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2fe45c71…dc5a
0x34b655…2a6f
6 touches
3 conflicts
0xf7f78508…6b24
0x34b655…2a6f
4 touches
1 conflict
0x1683d146…5ec2
0x34b655…2a6f
4 touches
1 conflict
0x1eb410fd…591d
0x34b655…2a6f
4 touches
1 conflict
0x31ec17e3…8913
0x34b655…2a6f
4 touches
1 conflict
0x31ec17e3…8912
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity