← previous blocknext block →recent activity
Analyzing
Block #95,572,243
18 transactions · 14 stateful · 2026-08-13 07:31:42 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,572,243 · 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
2w03w14w07w19w010w111w215w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f63a266…68c0
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x1dd68810…d641
0x34b655…2a6f
4 touches
1 conflict
0x1ebd4745…6509
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x32f9a4c9…60ec
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 0x7f63a2661a…b468c0
Audit this contract →
← previous block·next block →recent activity