← previous blocknext block →recent activity
Analyzing
Block #96,027,714
18 transactions · 17 stateful · 2026-08-14 21:44:08 UTC
Parallelism
56/100
Blocked
59%
Avg conflicts / tx
1.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,027,714 · 18 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
1w02w03w16w28w09w310w411w512w613w114w715w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bdb07b7…9d1b
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x155e52ca…fac7
0x34b655…2a6f
6 touches
3 conflicts
0x56153262…21ce
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xd0fd6c76…ddaf
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x4bdb07b70b…c39d1b
Audit this contract →
← previous block·next block →recent activity