← previous blocknext block →recent activity
Analyzing
Block #97,358,804
24 transactions · 21 stateful · 2026-08-19 13:40:32 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,358,804 · 24 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
1w02w03w16w08w19w210w312w414w515w116w222w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e56f6b6…5940
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xf688741e…7cad
0x34b655…2a6f
10 touches
10 conflicts
0xd79c9727…1233
0x34b655…2a6f
8 touches
6 conflicts
0x99c5409a…25b7
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x5060cdde…445d
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 0x1e56f6b6e1…615940
Audit this contract →
← previous block·next block →recent activity