← previous blocknext block →recent activity
Analyzing
Block #99,361,253
17 transactions · 14 stateful · 2026-08-26 15:11:02 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,361,253 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w010w112w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x167dc8aa…d65e
0x34b655…2a6f
2 touches
0 conflicts
0x17ff2059…ddb4
0x34b655…2a6f
2 touches
0 conflicts
0x1951ee47…540f
0x34b655…2a6f
2 touches
0 conflicts
0x21d5de02…3504
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
1 conflict on slot 0x261cbea79d…12e35d
Audit this contract →
← previous block·next block →recent activity