← previous blocknext block →recent activity
Analyzing
Block #97,467,293
18 transactions · 15 stateful · 2026-08-19 23:10:22 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,467,293 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w27w28w312w113w214w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5cfec795…7c0e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x30064b5f…0b1c
0x34b655…2a6f
6 touches
3 conflicts
0xb97c885b…2933
0x34b655…2a6f
6 touches
3 conflicts
0x2dcc0868…26bf
0x34b655…2a6f
6 touches
3 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity