← previous blocknext block →recent activity
Analyzing
Block #98,490,482
12 transactions · 12 stateful · 2026-08-23 13:27:01 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,490,482 · 12 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
1w02w13w04w26w07w18w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3663b826…bd5c
0x34b655…2a6f
6 touches
3 conflicts
0xa366dc41…b2d8
0xa6afd3…d132
4 touches
1 conflict
0xf346808d…6ad4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
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…001c
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 0x3663b82667…6abd5c
Audit this contract →
← previous block·next block →recent activity