← previous blocknext block →recent activity
Analyzing
Block #97,729,471
18 transactions · 15 stateful · 2026-08-20 21:22:27 UTC
Parallelism
89/100
Blocked
27%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,729,471 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w06w010w111w113w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0xda4a9eba…1e41
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x3aa71341…519c
0x34b655…2a6f
4 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0x45f562b2…9294
0x2b46c0…1669
2 touches
0 conflicts
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
1 conflict on slot 0xbcdd58ff98…970711
Audit this contract →
← previous block·next block →recent activity