← previous blocknext block →recent activity
Analyzing
Block #96,018,030
26 transactions · 21 stateful · 2026-08-14 20:55:26 UTC
Parallelism
65/100
Blocked
57%
Avg conflicts / tx
1.27
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #96,018,030 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w17w29w310w215w316w017w420w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x42f376fa…6766
0x34b655…2a6f
8 touches
6 conflicts
0x802741e7…56b9
0x34b655…2a6f
8 touches
6 conflicts
0x7084eabd…415b
0x34b655…2a6f
6 touches
3 conflicts
0x74462c1e…84f3
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
15 conflicts on slot 0x1a5d321d5d…0da474
Audit this contract →
← previous block·next block →recent activity