← previous blocknext block →recent activity
Analyzing
Block #97,842,378
17 transactions · 17 stateful · 2026-08-21 06:52:29 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,842,378 · 17 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
1w06w17w28w111w012w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadd5ff7c…8925
0x34b655…2a6f
8 touches
6 conflicts
0xacbe90a6…7d61
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf1ed798a…bb79
0x34b655…2a6f
4 touches
1 conflict
0x1479c05b…1a44
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
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 0xadd5ff7c3c…318925
Audit this contract →
← previous block·next block →recent activity