← previous blocknext block →recent activity
Analyzing
Block #96,296,869
12 transactions · 12 stateful · 2026-08-15 20:17:57 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,296,869 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w410w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0608dfe…083d
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x71142bc2…a79a
0x34b655…2a6f
6 touches
3 conflicts
0x60d93ca8…f522
0x34b655…2a6f
4 touches
1 conflict
0x85762bb0…c91c
0x34b655…2a6f
4 touches
1 conflict
0x9dd0a735…4d04
0x34b655…2a6f
4 touches
1 conflict
0x9f60dbd0…5f36
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 0xb0608dfe23…ab083d
Audit this contract →
← previous block·next block →recent activity