← previous blocknext block →recent activity
Analyzing
Block #99,447,247
18 transactions · 17 stateful · 2026-08-26 22:24:07 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,447,247 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w19w210w311w113w416w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe97d54c5…ef6f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xa3c36de0…3cf3
0x34b655…2a6f
6 touches
3 conflicts
0x70a80845…16d3
0x34b655…2a6f
6 touches
3 conflicts
0x6324ccc9…14fd
0x34b655…2a6f
4 touches
1 conflict
0x813075b0…e8bb
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
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
10 conflicts on slot 0xe97d54c5c1…33ef6f
Audit this contract →
← previous block·next block →recent activity