← previous blocknext block →recent activity
Analyzing
Block #97,371,131
19 transactions · 16 stateful · 2026-08-19 14:43:49 UTC
Parallelism
74/100
Blocked
31%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,371,131 · 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
6w08w09w110w111w213w017w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4360b49f…140d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6676e4f3…6a9e
0x851145…3f07
4 touches
1 conflict
0x0921dc9d…1c7f
0x34b655…2a6f
4 touches
1 conflict
0x11d9fe44…b676
0x34b655…2a6f
4 touches
1 conflict
0xb409e204…89ac
0x34b655…2a6f
4 touches
1 conflict
0xc2a8ecc5…5b56
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 0x4360b49f2d…54140d
Audit this contract →
← previous block·next block →recent activity