← previous blocknext block →recent activity
Analyzing
Block #97,556,659
31 transactions · 28 stateful · 2026-08-20 06:40:59 UTC
Parallelism
87/100
Blocked
36%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,556,659 · 31 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
2w04w09w010w011w112w116w117w218w019w120w221w123w328w029w130w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x246e5638…b635
0x34b655…2a6f
8 touches
6 conflicts
0x3eb83622…c15a
0x34b655…2a6f
8 touches
6 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x12070f84…331c
0xa6afd3…d132
4 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
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
6 conflicts on slot 0x246e5638a2…07b635
Audit this contract →
← previous block·next block →recent activity