← previous blocknext block →recent activity
Analyzing
Block #92,159,512
15 transactions · 13 stateful · 2026-08-01 08:53:12 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,159,512 · 15 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
1w06w07w18w29w010w111w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32790195…b240
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe8fc143b…4360
0x7b9256…1fb2
4 touches
1 conflict
0x9abf5f94…fc35
0x7b9256…1fb2
4 touches
1 conflict
0xe8fc143b…435c
0x7b9256…1fb2
4 touches
1 conflict
0xe8fc143b…435d
0x7b9256…1fb2
4 touches
1 conflict
0x0170241a…a745
0x34b655…2a6f
4 touches
1 conflict
0x4786839b…c29a
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
3 conflicts on slot 0x3279019527…69b240
Audit this contract →
← previous block·next block →recent activity