← previous blocknext block →recent activity
Analyzing
Block #96,046,764
13 transactions · 13 stateful · 2026-08-14 23:20:00 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,046,764 · 13 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
3w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0xe73b93bf…c0e1
0x34b655…2a6f
4 touches
1 conflict
0xbf6cd801…0d01
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x16f8e14a…f6e4
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x69880b42…db5b
0x34b655…2a6f
2 touches
0 conflicts
0x7ee6007b…fd68
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 0x727fbce74b…da0c80
Audit this contract →
← previous block·next block →recent activity