← previous blocknext block →recent activity
Analyzing
Block #95,370,223
27 transactions · 23 stateful · 2026-08-12 14:33:53 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,370,223 · 27 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
1w02w13w25w38w09w113w014w117w220w423w326w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37eae3e2…7724
0x34b655…2a6f
6 touches
3 conflicts
0xf8c80ea7…780d
0xd32edf…ff58
5 touches
3 conflicts
0x042a69f6…2e84
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x28cde80e…b851
0x34b655…2a6f
4 touches
1 conflict
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0xa4732d87…2eff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641d
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 0x37eae3e2b5…fc7724
Audit this contract →
← previous block·next block →recent activity