← previous blocknext block →recent activity
Analyzing
Block #95,784,306
10 transactions · 7 stateful · 2026-08-14 01:19:21 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,784,306 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66ae117a…0e93
0x34b655…2a6f
4 touches
1 conflict
0x925dfa51…2cba
0x34b655…2a6f
4 touches
1 conflict
0xbc89da14…a1b5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 conflicts
0x02bf7faf…ca0e
0x34b655…2a6f
2 touches
0 conflicts
0x0cd89b3c…836c
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x66ae117a5d…a50e93
Audit this contract →
← previous block·next block →recent activity