← previous blocknext block →recent activity
Analyzing
Block #98,325,111
16 transactions · 14 stateful · 2026-08-22 23:34:42 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,325,111 · 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
4w06w07w19w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x074c08f8…fb56
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xed903df2…6ea4
0x34b655…2a6f
4 touches
1 conflict
0xf2dc7074…4491
0x34b655…2a6f
4 touches
1 conflict
0x03b45b78…471d
0x34b655…2a6f
4 touches
1 conflict
0x53e50026…6d8c
0x2b46c0…1669
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 0x074c08f891…02fb56
Audit this contract →
← previous block·next block →recent activity