← previous blocknext block →recent activity
Analyzing
Block #92,066,204
10 transactions · 10 stateful · 2026-08-01 01:03:54 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,066,204 · 10 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
1w02w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x01e4765d…2502
0x34b655…2a6f
2 touches
0 conflicts
0x22a7d1f2…aafe
0x34b655…2a6f
2 touches
0 conflicts
0x2385516f…eca5
0x34b655…2a6f
2 touches
0 conflicts
0x427c9fc4…5cee
0x34b655…2a6f
2 touches
0 conflicts
0x78595b9f…6aab
0x34b655…2a6f
2 touches
0 conflicts
0x89a711f8…aaed
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 0x6d1b72eefe…416b78
Audit this contract →
← previous block·next block →recent activity