← previous blocknext block →recent activity
Analyzing
Block #97,371,347
21 transactions · 17 stateful · 2026-08-19 14:44:54 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
1.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,371,347 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w211w112w213w314w415w316w418w520w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4360b49f…140d
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xf18906a6…d2e3
0x34b655…2a6f
8 touches
6 conflicts
0x4e37574f…4145
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92b49f44…ee4f
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
15 conflicts on slot 0x4360b49f2d…54140d
Audit this contract →
← previous block·next block →recent activity