← previous blocknext block →recent activity
Analyzing
Block #97,185,547
15 transactions · 14 stateful · 2026-08-18 23:00:52 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,185,547 · 15 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
1w04w05w16w27w08w19w311w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6000ba5…8d65
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa9afe8da…0218
0x754704…b603
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0xc6b9bb4b…145a
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 0xc6000ba5c1…988d65
Audit this contract →
← previous block·next block →recent activity