← previous blocknext block →recent activity
Analyzing
Block #97,360,023
17 transactions · 17 stateful · 2026-08-19 13:46:50 UTC
Parallelism
59/100
Blocked
41%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,360,023 · 17 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
1w05w16w17w28w39w413w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x320c463e…b79a
0x34b655…2a6f
10 touches
10 conflicts
0xc6b604e6…5152
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x9a9383a9…6bc7
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x320c463e1b…11b79a
Audit this contract →
← previous block·next block →recent activity