← previous blocknext block →recent activity
Analyzing
Block #99,191,022
18 transactions · 17 stateful · 2026-08-26 00:54:25 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,191,022 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w09w113w014w115w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9add604…028b
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x89ac61bf…9443
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xaae6463e…bfcc
0x34b655…2a6f
4 touches
1 conflict
0xd8e95e71…7c00
0x34b655…2a6f
4 touches
1 conflict
0xe251ba03…50f8
0x34b655…2a6f
4 touches
1 conflict
0xfa09be5a…1e79
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 0xa9add60413…86028b
Audit this contract →
← previous block·next block →recent activity