← previous blocknext block →recent activity
Analyzing
Block #95,626,620
18 transactions · 16 stateful · 2026-08-13 12:05:13 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,626,620 · 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
1w03w14w05w012w213w114w215w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6da49392…3791
0x34b655…2a6f
6 touches
3 conflicts
0x9577c5b8…b791
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x4c619b7d…f4fa
0x34b655…2a6f
4 touches
1 conflict
0x5a19ef35…dc70
0x34b655…2a6f
4 touches
1 conflict
0x87ebdc37…8cad
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcf17589f…048c
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 0x6da493920e…ca3791
Audit this contract →
← previous block·next block →recent activity