← previous blocknext block →recent activity
Analyzing
Block #97,898,306
16 transactions · 16 stateful · 2026-08-21 11:40:59 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,898,306 · 16 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
5w06w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4a1
0x34b655…2a6f
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x78b187ff…a000
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebf3
0x77d53b…8080
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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 0x7e5ea60ab2…b0c4a1
Audit this contract →
← previous block·next block →recent activity