← previous blocknext block →recent activity
Analyzing
Block #99,162,487
13 transactions · 13 stateful · 2026-08-25 22:30:51 UTC
Parallelism
54/100
Blocked
54%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,162,487 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w28w39w410w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09f9a86a…1e22
0x34b655…2a6f
6 touches
3 conflicts
0xea57afd0…4232
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
4 touches
1 conflict
0x8488f10f…9353
0x2b46c0…1669
4 touches
1 conflict
0xa17ec269…7cdd
0x2b46c0…1669
4 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
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 0x09f9a86a30…d91e22
Audit this contract →
← previous block·next block →recent activity