← previous blocknext block →recent activity
Analyzing
Block #95,079,576
19 transactions · 18 stateful · 2026-08-11 14:00:04 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,079,576 · 19 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
2w03w16w27w08w19w210w311w415w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa19591ca…ba31
0x34b655…2a6f
6 touches
3 conflicts
0xe7d2a532…f5a5
0x34b655…2a6f
6 touches
3 conflicts
0x59bfb0ed…ebd2
0x34b655…2a6f
4 touches
1 conflict
0x5d6e4470…4b4c
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xd6db9d1c…2f37
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: 0xe52b1424…bb7230
10 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity