← previous blocknext block →recent activity
Analyzing
Block #92,110,177
37 transactions · 36 stateful · 2026-08-01 04:45:02 UTC
Parallelism
92/100
Blocked
14%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,110,177 · 37 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w19w126w235w036w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe708efe…df34
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x4ef8d411…f9a0
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0xecd9ff68…d469
0x34b655…2a6f
4 touches
1 conflict
0xff3dbbcd…5060
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 0xfe708efe93…b8df34
Audit this contract →
← previous block·next block →recent activity