← previous blocknext block →recent activity
Analyzing
Block #95,747,054
23 transactions · 23 stateful · 2026-08-13 22:12:01 UTC
Parallelism
83/100
Blocked
61%
Avg conflicts / tx
1.13
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,747,054 · 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
1w02w14w05w06w17w18w29w210w311w312w113w014w115w216w317w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60ea44fe…fb25
0x968279…9342
8 touches
6 conflicts
0x60ea44fe…fb26
0x968279…9342
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xa6d28e45…7609
0x968279…9342
8 touches
6 conflicts
0xa6d28e45…760b
0x968279…9342
8 touches
6 conflicts
0xa6d28e45…7608
0x968279…9342
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x60ea44fe…fb27
0x968279…9342
8 touches
6 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: 0x96827978…f09342
6 conflicts on slot 0x60ea44fef2…9ffb25
Audit this contract →
← previous block·next block →recent activity