← previous blocknext block →recent activity
Analyzing
Block #99,606,463
20 transactions · 19 stateful · 2026-08-27 11:50:38 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,606,463 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w18w09w010w112w113w214w318w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70d81211…f49f
0x34b655…2a6f
6 touches
3 conflicts
0x1d9154e7…8821
0x34b655…2a6f
6 touches
3 conflicts
0x674f0308…55e3
0x34b655…2a6f
6 touches
3 conflicts
0x72d657f8…d7b7
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x80b000d3…1c9d
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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: Perpl
3 conflicts on slot 0x70d812119d…c1f49f
Audit this contract →
← previous block·next block →recent activity