← previous blocknext block →recent activity
Analyzing
Block #97,546,063
17 transactions · 15 stateful · 2026-08-20 05:46:53 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,546,063 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w011w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf80e177…646c
0x34b655…2a6f
4 touches
1 conflict
0x3e1b765a…ae54
0x34b655…2a6f
4 touches
1 conflict
0x59a84baf…4dfa
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf9a57445…8ac2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x42b70c04…f512
0x40c49f…2af0
3 touches
1 conflict
0x46cb45de…a568
0x188d58…ea8e
2 touches
0 conflicts
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
1 conflict on slot 0xcf80e1776a…ee646c
Audit this contract →
← previous block·next block →recent activity