← previous blocknext block →recent activity
Analyzing
Block #99,279,003
18 transactions · 16 stateful · 2026-08-26 08:17:08 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,279,003 · 18 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
5w06w18w09w112w216w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf33458c2…44bf
0x34b655…2a6f
4 touches
1 conflict
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x91508d45…318b
0x34b655…2a6f
4 touches
1 conflict
0xb38fa121…0c8b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x260cc5c4…bef0
0x2b46c0…1669
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
1 conflict on slot 0xf33458c2de…f244bf
Audit this contract →
← previous block·next block →recent activity