← previous blocknext block →recent activity
Analyzing
Block #92,968,691
8 transactions · 7 stateful · 2026-08-04 04:44:32 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,968,691 · 8 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0x0b0611f7…e63a
0x34b655…2a6f
4 touches
1 conflict
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0x38bdc5d3…a632
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x641aed07…bcb9
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 0x038b92433d…c5553d
Audit this contract →
← previous block·next block →recent activity