← previous blocknext block →recent activity
Analyzing
Block #97,466,114
19 transactions · 19 stateful · 2026-08-19 23:04:27 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.26
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,466,114 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w17w28w29w310w311w412w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xcdb8aa5c…a640
0x34b655…2a6f
4 touches
1 conflict
0x806c6904…3d63
0x34b655…2a6f
4 touches
1 conflict
0x331a294a…7f59
0x34b655…2a6f
4 touches
1 conflict
0x75fe24d2…46f9
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
2 touches
0 conflicts
0x6771eae2…7014
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
15 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity