← previous blocknext block →recent activity
Analyzing
Block #97,478,502
18 transactions · 16 stateful · 2026-08-20 00:07:00 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,478,502 · 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
3w04w05w16w17w28w39w010w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda1f3e2c…b73d
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xba9ffde8…207c
0x34b655…2a6f
4 touches
1 conflict
0xbb201fc1…4e05
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdeaa385f…6b8b
0x34b655…2a6f
4 touches
1 conflict
0xea79e6d3…68ad
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
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 0xda1f3e2ca4…a6b73d
Audit this contract →
← previous block·next block →recent activity