← previous blocknext block →recent activity
Analyzing
Block #96,489,047
9 transactions · 7 stateful · 2026-08-16 12:24:31 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,489,047 · 9 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
4w05w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84ee6168…3f13
0x34b655…2a6f
6 touches
3 conflicts
0xf5f815e7…c83e
0x34b655…2a6f
6 touches
3 conflicts
0xd3a1fb6a…5e50
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x44f26cbe…58c2
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9c0cdadd…1574
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
3 conflicts on slot 0x84ee616829…843f13
Audit this contract →
← previous block·next block →recent activity