← previous blocknext block →recent activity
Analyzing
Block #99,958,012
35 transactions · 35 stateful · 2026-08-28 17:28:53 UTC
Parallelism
57/100
Blocked
63%
Avg conflicts / tx
3.43
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #99,958,012 · 35 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w07w18w211w012w013w114w115w116w017w118w219w320w421w522w623w724w825w926w1027w1128w1229w1332w334w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51ee0faa…d7af
0x912009…bb53
30 touches
105 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x27b6010e…e4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00e21a9f…3583
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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: 0x9120090c…dfbb53
105 conflicts on slot 0x51ee0faaba…e5d7af
Audit this contract →
← previous block·next block →recent activity