← previous blocknext block →recent activity
Analyzing
Block #97,562,118
17 transactions · 16 stateful · 2026-08-20 07:08:50 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,562,118 · 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
1w04w06w17w210w311w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e2cb5a0…bf4f
0x34b655…2a6f
8 touches
6 conflicts
0xa38c430a…e3cb
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x92a60d6d…ebe8
0x34b655…2a6f
6 touches
3 conflicts
0x6219536c…a4f1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
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 0x9e2cb5a0e2…b0bf4f
Audit this contract →
← previous block·next block →recent activity