← previous blocknext block →recent activity
Analyzing
Block #92,760,516
13 transactions · 12 stateful · 2026-08-03 11:17:00 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,760,516 · 13 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
0x8a1e429b…f85c
0x34b655…2a6f
4 touches
1 conflict
0x921a7f27…4264
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x46c64ae6…6a06
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0xa3e2ef33…acfd
0x34b655…2a6f
3 touches
1 conflict
0x6d9570ad…fb24
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 0x8a1e429b94…e9f85c
Audit this contract →
← previous block·next block →recent activity