← previous blocknext block →recent activity
Analyzing
Block #96,510,618
8 transactions · 8 stateful · 2026-08-16 14:13:19 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,510,618 · 8 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73670e81…2813
0x34b655…2a6f
8 touches
6 conflicts
0x3727225e…a3cf
0x34b655…2a6f
6 touches
3 conflicts
0xfaf0f79f…6722
0x34b655…2a6f
4 touches
1 conflict
0x3c7c65d0…0b52
0x34b655…2a6f
4 touches
1 conflict
0x9a573905…60cf
0x34b655…2a6f
4 touches
1 conflict
0xa457c06e…2f06
0x34b655…2a6f
4 touches
1 conflict
0xa6848351…2238
0x34b655…2a6f
4 touches
1 conflict
0xc01decc3…08a1
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: Perpl
6 conflicts on slot 0x73670e81ae…572813
Audit this contract →
← previous block·next block →recent activity