← previous blocknext block →recent activity
Analyzing
Block #97,841,142
23 transactions · 21 stateful · 2026-08-21 06:46:11 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,841,142 · 23 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
1w02w03w17w08w09w110w111w213w114w218w019w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x901b2a81…7af9
0xa6afd3…d132
4 touches
1 conflict
0x29be38f0…7bb1
0x40c49f…2af0
4 touches
1 conflict
0x3fdb897f…5707
0x40c49f…2af0
4 touches
1 conflict
0xa149f0ce…4d65
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x7f9622bd…ef05
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity