← previous blocknext block →recent activity
Analyzing
Block #98,206,586
24 transactions · 24 stateful · 2026-08-22 13:38:21 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,206,586 · 24 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
1w02w03w05w16w08w010w011w112w113w214w215w017w319w121w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xf1ba35db…8e8f
0x34b655…2a6f
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x0e682ed1…657d
0x34b655…2a6f
4 touches
1 conflict
0x14cc77c7…69c4
0x34b655…2a6f
4 touches
1 conflict
0x168f7615…a8de
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
1 conflict on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity