← previous blocknext block →recent activity
Analyzing
Block #92,202,433
69 transactions · 68 stateful · 2026-08-01 12:29:01 UTC
Parallelism
97/100
Blocked
1%
Avg conflicts / tx
0.01
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,202,433 · 69 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
2w067w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e8a26ca…0257
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8c1b3662…8075
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc550cc48…815d
0x34b655…2a6f
4 touches
1 conflict
0xc550cc48…815e
0x34b655…2a6f
4 touches
1 conflict
0xe7ceda84…1a3e
0x34b655…2a6f
4 touches
1 conflict
0x2328941c…84d3
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 0x6e8a26ca29…e10257
Audit this contract →
← previous block·next block →recent activity