← previous blocknext block →recent activity
Analyzing
Block #99,709,667
13 transactions · 13 stateful · 2026-08-27 20:33:45 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,709,667 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w08w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e49348b…9445
0x34b655…2a6f
6 touches
3 conflicts
0x57e5abc1…286f
0x34b655…2a6f
6 touches
3 conflicts
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002d
0x1b6862…e19c
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
3 conflicts on slot 0x3e49348b38…839445
Audit this contract →
← previous block·next block →recent activity