← previous blocknext block →recent activity
Analyzing
Block #95,596,943
16 transactions · 14 stateful · 2026-08-13 09:35:56 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,596,943 · 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
2w03w14w27w39w010w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ffb6fe7…ddc7
0x34b655…2a6f
8 touches
6 conflicts
0x0b34a794…400b
0x34b655…2a6f
4 touches
1 conflict
0x103b26fe…1130
0x34b655…2a6f
4 touches
1 conflict
0x10797f0b…439a
0x34b655…2a6f
4 touches
1 conflict
0x3859e735…be12
0x34b655…2a6f
4 touches
1 conflict
0x3cd30038…c5af
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x481b500f…7ef3
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 0x6ffb6fe758…f2ddc7
Audit this contract →
← previous block·next block →recent activity