← previous blocknext block →recent activity
Analyzing
Block #97,519,515
28 transactions · 23 stateful · 2026-08-20 03:33:20 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,519,515 · 28 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
1w02w13w25w06w110w012w116w017w018w119w220w321w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe88f66fe…579f
0x34b655…2a6f
6 touches
3 conflicts
0xdc84ae3f…4c7e
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x9ac040c1…8220
0x1b6862…e19c
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
3 conflicts on slot 0xe88f66fe6c…1e579f
Audit this contract →
← previous block·next block →recent activity