← previous blocknext block →recent activity
Analyzing
Block #96,666,639
40 transactions · 40 stateful · 2026-08-17 03:18:02 UTC
Parallelism
92/100
Blocked
10%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,666,639 · 40 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w234w035w138w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbe6a366…8ca1
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x34d4ef1a…0345
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x24b7fda3…37f2
0x34b655…2a6f
2 touches
0 conflicts
0x24ca1902…7a87
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
3 conflicts on slot 0xfbe6a36638…508ca1
Audit this contract →
← previous block·next block →recent activity