← previous blocknext block →recent activity
Analyzing
Block #97,606,047
18 transactions · 15 stateful · 2026-08-20 10:51:13 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,606,047 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w07w08w19w210w311w012w116w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33ebc453…a0f7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2e5cdd04…22ab
0x34b655…2a6f
6 touches
3 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xd996735f…8731
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x08a9d59a…a7cf
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 0x33ebc453f9…e1a0f7
Audit this contract →
← previous block·next block →recent activity