← previous blocknext block →recent activity
Analyzing
Block #97,628,170
19 transactions · 16 stateful · 2026-08-20 12:42:58 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,628,170 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w010w112w413w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xcefb6f53…914a
0x34b655…2a6f
6 touches
3 conflicts
0x3fb8d6f7…6f61
0x34b655…2a6f
6 touches
3 conflicts
0xcc6fb243…139f
0x34b655…2a6f
4 touches
1 conflict
0xc2044b9c…c271
0xa6afd3…d132
4 touches
1 conflict
0xa5cee576…65ae
0xa6afd3…d132
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity