← previous blocknext block →recent activity
Analyzing
Block #95,180,124
18 transactions · 17 stateful · 2026-08-11 22:25:50 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,180,124 · 18 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
1w02w14w05w17w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8266c16e…3699
0x40c49f…2af0
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0x6518075e…2b17
0x2a68ba…90c5
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xcc3207c1…fad6
0x34b655…2a6f
4 touches
1 conflict
0x52037bd1…2ad8
0xd18b7e…414b
4 touches
1 conflict
0xf3d10975…0d07
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: 0x40c49f17…d22af0
6 conflicts on slot 0x8266c16e41…cd3699
Audit this contract →
← previous block·next block →recent activity