← previous blocknext block →recent activity
Analyzing
Block #95,736,604
10 transactions · 7 stateful · 2026-08-13 21:19:27 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,736,604 · 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
1w02w14w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3a4411d…81af
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x44eeb5f8…5b79
0x065c9d…c394
2 touches
0 conflicts
0x9dd21619…1ea0
0x065c9d…c394
2 touches
0 conflicts
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
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 0xd3a4411d7c…9581af
Audit this contract →
← previous block·next block →recent activity