← previous blocknext block →recent activity
Analyzing
Block #95,524,192
16 transactions · 13 stateful · 2026-08-13 03:30:01 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,524,192 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w18w09w010w112w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xff68510a…09f1
0x34b655…2a6f
6 touches
3 conflicts
0x8163be7f…cc7e
0x34b655…2a6f
6 touches
3 conflicts
0xd530190b…8c24
0x34b655…2a6f
6 touches
3 conflicts
0x51a5d485…912a
0x34b655…2a6f
4 touches
1 conflict
0x587cee80…30cc
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity