← previous blocknext block →recent activity
Analyzing
Block #97,530,768
19 transactions · 17 stateful · 2026-08-20 04:29:57 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,530,768 · 19 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
1w02w03w16w07w18w29w310w314w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x038cc908…508b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x351f4dd5…7d10
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x54f7f60f23…cb43cc
Audit this contract →
← previous block·next block →recent activity