← previous blocknext block →recent activity
Analyzing
Block #97,684,038
16 transactions · 12 stateful · 2026-08-20 17:31:54 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,684,038 · 16 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
4w05w16w29w210w315w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe70f6c1d…2539
0x34b655…2a6f
6 touches
3 conflicts
0x736c5b69…fb3f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xea2dfc3b…a014
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
3 conflicts on slot 0xe70f6c1de1…fc2539
Audit this contract →
← previous block·next block →recent activity