← previous blocknext block →recent activity
Analyzing
Block #96,374,087
10 transactions · 9 stateful · 2026-08-16 02:46:20 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,374,087 · 10 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
3w04w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1faa605…f919
0x34b655…2a6f
6 touches
3 conflicts
0x1bd69a6a…2b8a
0x34b655…2a6f
4 touches
1 conflict
0x73670e81…2813
0x34b655…2a6f
4 touches
1 conflict
0x7da56943…9753
0x34b655…2a6f
4 touches
1 conflict
0x8cdaab66…f6e8
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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 0xf1faa605a5…02f919
Audit this contract →
← previous block·next block →recent activity