← previous blocknext block →recent activity
Analyzing
Block #99,667,681
24 transactions · 20 stateful · 2026-08-27 17:00:59 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,667,681 · 24 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
1w02w13w04w05w08w19w014w115w016w117w118w019w122w023w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61e88b60…c8ec
0x40c49f…2af0
4 touches
1 conflict
0xfdd131fa…dbdb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x22db2187…cb6b
0x34b655…2a6f
4 touches
1 conflict
0x31c4594c…ede7
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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: 0x40c49f17…d22af0
1 conflict on slot 0x61e88b60d8…ebc8ec
Audit this contract →
← previous block·next block →recent activity