← previous blocknext block →recent activity
Analyzing
Block #97,495,918
18 transactions · 13 stateful · 2026-08-20 01:34:37 UTC
Parallelism
72/100
Blocked
46%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,495,918 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w18w29w211w312w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x015a51cb…b7b7
0x34b655…2a6f
8 touches
6 conflicts
0x5c116bcd…262c
0x34b655…2a6f
6 touches
3 conflicts
0xce23d849…c7b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xb779f9ac…5f94
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
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 0x015a51cb01…f4b7b7
Audit this contract →
← previous block·next block →recent activity