← previous blocknext block →recent activity
Analyzing
Block #99,874,821
13 transactions · 12 stateful · 2026-08-28 10:29:38 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,874,821 · 13 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
3w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa5537c0…b528
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x359866c7…de7b
0x34b655…2a6f
4 touches
1 conflict
0x36821062…c107
0x34b655…2a6f
2 touches
0 conflicts
0x3d2a5764…3d08
0x34b655…2a6f
2 touches
0 conflicts
0x75691f4f…f8a7
0x34b655…2a6f
2 touches
0 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
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 0xfa5537c040…5bb528
Audit this contract →
← previous block·next block →recent activity