← previous blocknext block →recent activity
Analyzing
Block #95,915,184
20 transactions · 19 stateful · 2026-08-14 12:17:54 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,915,184 · 20 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
2w03w14w05w16w17w28w111w213w015w118w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda46a376…f6a6
0x34b655…2a6f
8 touches
6 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x0f6aef87…8137
0x34b655…2a6f
6 touches
3 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
6 touches
3 conflicts
0x02991b41…19e6
0x34b655…2a6f
6 touches
3 conflicts
0x2b0014f5…614e
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
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
6 conflicts on slot 0xda46a376d7…59f6a6
Audit this contract →
← previous block·next block →recent activity