← previous blocknext block →recent activity
Analyzing
Block #97,369,052
19 transactions · 17 stateful · 2026-08-19 14:33:10 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,369,052 · 19 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
2w03w04w15w26w07w19w312w413w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f1df4c1…d7da
0x34b655…2a6f
10 touches
10 conflicts
0x6771eae2…7014
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x379dc435…6616
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x706ef219…91fa
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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
10 conflicts on slot 0x8f1df4c19b…31d7da
Audit this contract →
← previous block·next block →recent activity