← previous blocknext block →recent activity
Analyzing
Block #97,480,396
19 transactions · 16 stateful · 2026-08-20 00:16:32 UTC
Parallelism
63/100
Blocked
63%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,480,396 · 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
1w03w05w16w27w38w49w110w011w112w213w514w115w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x516e9b35…57e7
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
6 touches
3 conflicts
0x9bcefb9c…07b3
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x9cf9008a…d826
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
6 conflicts on slot 0x516e9b35e5…8857e7
Audit this contract →
← previous block·next block →recent activity