← previous blocknext block →recent activity
Analyzing
Block #97,356,978
44 transactions · 37 stateful · 2026-08-19 13:30:59 UTC
Parallelism
68/100
Blocked
65%
Avg conflicts / tx
1.95
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,356,978 · 44 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w07w18w09w110w211w312w413w514w615w716w823w925w1026w1129w1231w132w243w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0xf3383813…4a0c
0x34b655…2a6f
10 touches
10 conflicts
0x67a56c8b…f955
0x34b655…2a6f
10 touches
10 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
10 touches
10 conflicts
0xc9f7b83f…a184
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity