← previous blocknext block →recent activity
Analyzing
Block #92,172,101
16 transactions · 14 stateful · 2026-08-01 09:56:30 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,172,101 · 16 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
2w04w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1eb410fd…591d
0x34b655…2a6f
4 touches
1 conflict
0x0f427418…2a49
0x34b655…2a6f
4 touches
1 conflict
0x0216a577…5bd8
0x34b655…2a6f
4 touches
1 conflict
0x4b17bb5b…b3d4
0x34b655…2a6f
4 touches
1 conflict
0xdeb02fe5…8e82
0x34b655…2a6f
4 touches
1 conflict
0xfb4f6c11…7103
0x34b655…2a6f
4 touches
1 conflict
0x2308373a…5f9b
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
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 0x1eb410fdc2…cd591d
Audit this contract →
← previous block·next block →recent activity