← previous blocknext block →recent activity
Analyzing
Block #97,548,124
22 transactions · 21 stateful · 2026-08-20 05:57:15 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,548,124 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w19w210w014w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x713db58f…6ff9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xc8c615d4…5da3
0x34b655…2a6f
4 touches
1 conflict
0xf7bfb5fd…cb38
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xae5c64bf…6df7
0x40c49f…2af0
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x20d11f04…4dc8
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
3 conflicts on slot 0x713db58fc3…1d6ff9
Audit this contract →
← previous block·next block →recent activity