← previous blocknext block →recent activity
Analyzing
Block #96,600,916
17 transactions · 17 stateful · 2026-08-16 21:47:29 UTC
Parallelism
53/100
Blocked
41%
Avg conflicts / tx
1.59
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,600,916 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w29w310w411w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x8dca726c…af0b
0x34b655…2a6f
10 touches
10 conflicts
0x31616f97…1acc
0x34b655…2a6f
10 touches
10 conflicts
0x5d1ac445…5233
0x34b655…2a6f
6 touches
3 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
6 touches
3 conflicts
0x57a9b62e…08c1
0x34b655…2a6f
4 touches
1 conflict
0x6af385b8…971b
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity