← previous blocknext block →recent activity
Analyzing
Block #96,684,265
10 transactions · 9 stateful · 2026-08-17 04:46:40 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,684,265 · 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
5w06w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x8c8b1507…9a97
0x065c9d…c394
3 touches
1 conflict
0x7ace0b0d…d7a0
0x065c9d…c394
3 touches
1 conflict
0xdaf4f143…58d4
0x2a68ba…90c5
2 touches
0 conflicts
0x177f744d…b7dd
0x34b655…2a6f
2 touches
0 conflicts
0x8b37f931…1b3f
0x34b655…2a6f
2 touches
0 conflicts
0xb7fa6bb8…32f8
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 0x6d1b72eefe…416b78
Audit this contract →
← previous block·next block →recent activity