← previous blocknext block →recent activity
Analyzing
Block #97,431,845
17 transactions · 17 stateful · 2026-08-19 20:11:42 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,431,845 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w210w111w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc888b37…732c
0x8964d7…10f8
4 touches
1 conflict
0xdc888b37…7326
0x8964d7…10f8
4 touches
1 conflict
0xdc888b37…7327
0x8964d7…10f8
4 touches
1 conflict
0xdc888b37…732a
0x8964d7…10f8
4 touches
1 conflict
0xdc888b37…732b
0x8964d7…10f8
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc3961304…d676
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xdc888b373f…ca732c
Audit this contract →
← previous block·next block →recent activity