← previous blocknext block →recent activity
Analyzing
Block #92,319,036
13 transactions · 11 stateful · 2026-08-01 22:15:28 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,319,036 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w27w39w010w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb84f537…c9b2
0x34b655…2a6f
6 touches
3 conflicts
0x9673ce91…8672
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x378d61e4…7f15
0x34b655…2a6f
3 touches
1 conflict
0xba5743c7…21c0
0x1b6862…e19c
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
3 conflicts on slot 0xbb84f537ea…aec9b2
Audit this contract →
← previous block·next block →recent activity