← previous blocknext block →recent activity
Analyzing
Block #97,397,936
27 transactions · 23 stateful · 2026-08-19 17:19:42 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,397,936 · 27 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
1w02w03w04w15w26w07w38w415w120w021w124w525w626w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57a454d0…d63e
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x14df976b…0aa1
0x34b655…2a6f
4 touches
1 conflict
0x74aab31b…6bd1
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x00000000…003d
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
21 conflicts on slot 0x57a454d0c6…e9d63e
Audit this contract →
← previous block·next block →recent activity