← previous blocknext block →recent activity
Analyzing
Block #99,118,839
19 transactions · 17 stateful · 2026-08-25 18:51:15 UTC
Parallelism
84/100
Blocked
12%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,118,839 · 19 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
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d03bddb…6658
0x34b655…2a6f
6 touches
3 conflicts
0xbad4e90b…33a5
0x34b655…2a6f
4 touches
1 conflict
0xad07bbe5…a6da
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x24114bb9…acbc
0x34b655…2a6f
2 touches
0 conflicts
0x24d47694…e647
0x34b655…2a6f
2 touches
0 conflicts
0x2fbf2475…bbc3
0x34b655…2a6f
2 touches
0 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
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 0x0d03bddb26…a56658
Audit this contract →
← previous block·next block →recent activity