← previous blocknext block →recent activity
Analyzing
Block #92,079,166
12 transactions · 10 stateful · 2026-08-01 02:09:05 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,079,166 · 12 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
2w03w04w15w06w07w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2170bea4…4722
0x34b655…2a6f
4 touches
1 conflict
0x2170bea4…4723
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x3bb514bf…2967
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
4 touches
1 conflict
0x6a9db6e3…233a
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
1 conflict on slot 0x2170bea417…5f4722
Audit this contract →
← previous block·next block →recent activity