← previous blocknext block →recent activity
Analyzing
Block #95,087,947
24 transactions · 19 stateful · 2026-08-11 14:42:10 UTC
Parallelism
79/100
Blocked
26%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,087,947 · 24 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
6w08w09w111w212w315w016w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9adb2803…81f1
0x34b655…2a6f
10 touches
10 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6d7ace39…01fe
0x34b655…2a6f
4 touches
1 conflict
0x7b42f6a7…f49c
0x34b655…2a6f
4 touches
1 conflict
0xc73fd549…2e28
0x851145…3f07
4 touches
1 conflict
0x0600e909…c4f2
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
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
10 conflicts on slot 0x9adb2803c1…a181f1
Audit this contract →
← previous block·next block →recent activity