← previous blocknext block →recent activity
Analyzing
Block #99,486,256
13 transactions · 12 stateful · 2026-08-27 01:40:33 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,486,256 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36918c55…8424
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd4d1b191…3457
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x55010ec8…ea31
0x34b655…2a6f
2 touches
0 conflicts
0x97722e39…32e6
0x34b655…2a6f
2 touches
0 conflicts
0xb1856468…e84f
0x34b655…2a6f
2 touches
0 conflicts
0xb276222e…49c7
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
6 conflicts on slot 0x36918c5535…2c8424
Audit this contract →
← previous block·next block →recent activity