← previous blocknext block →recent activity
Analyzing
Block #92,972,675
14 transactions · 13 stateful · 2026-08-04 05:04:34 UTC
Parallelism
57/100
Blocked
54%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,972,675 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w07w28w19w010w311w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2385516f…eca5
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0x061849c3…d2ae
0x34b655…2a6f
5 touches
3 conflicts
0x979044e3…33d7
0x34b655…2a6f
4 touches
1 conflict
0xa56e54d0…2d39
0x34b655…2a6f
4 touches
1 conflict
0xfa551be3…a911
0xa6afd3…d132
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 0x2385516f6a…9aeca5
Audit this contract →
← previous block·next block →recent activity