← previous blocknext block →recent activity
Analyzing
Block #95,074,943
23 transactions · 21 stateful · 2026-08-11 13:36:45 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,074,943 · 23 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
1w02w03w14w25w06w17w08w29w310w011w117w022w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c676afe…440e
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0x42b10c57…3ee7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
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 0x4c676afecf…b3440e
Audit this contract →
← previous block·next block →recent activity