← previous blocknext block →recent activity
Analyzing
Block #95,985,124
16 transactions · 16 stateful · 2026-08-14 18:09:47 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,985,124 · 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
2w04w17w28w09w110w211w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35a9f06c…7689
0x34b655…2a6f
8 touches
6 conflicts
0xd88fd339…7801
0x968279…9342
6 touches
3 conflicts
0x3af1a628…ee17
0x968279…9342
6 touches
3 conflicts
0x3af1a628…ee1a
0x968279…9342
6 touches
3 conflicts
0x3af1a628…ee1b
0x968279…9342
6 touches
3 conflicts
0x3af1a628…ee1d
0x968279…9342
6 touches
3 conflicts
0xd88fd339…77fe
0x968279…9342
6 touches
3 conflicts
0xd88fd339…77ff
0x968279…9342
6 touches
3 conflicts
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 0x35a9f06ccf…e37689
Audit this contract →
← previous block·next block →recent activity