← previous blocknext block →recent activity
Analyzing
Block #97,842,979
18 transactions · 16 stateful · 2026-08-21 06:55:36 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,842,979 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w08w19w216w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd7cbc61…c07d
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x17ce7874…0569
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x97fcbc71…9660
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
1 conflict on slot 0xfd7cbc6167…19c07d
Audit this contract →
← previous block·next block →recent activity