← previous blocknext block →recent activity
Analyzing
Block #96,016,910
14 transactions · 12 stateful · 2026-08-14 20:49:47 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,016,910 · 14 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
4w05w18w29w311w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31616f97…1acc
0x34b655…2a6f
6 touches
3 conflicts
0x841318e5…3005
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0fb9e50c…1a35
0x34b655…2a6f
2 touches
0 conflicts
0x1507536e…933f
0x34b655…2a6f
2 touches
0 conflicts
0x23153440…0007
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
3 conflicts on slot 0x31616f9701…df1acc
Audit this contract →
← previous block·next block →recent activity