← previous blocknext block →recent activity
Analyzing
Block #98,550,584
37 transactions · 23 stateful · 2026-08-23 18:39:03 UTC
Parallelism
92/100
Blocked
30%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,550,584 · 37 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
1w03w16w010w011w021w023w124w127w028w129w131w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0xc0ae39b0…be5f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x6d352690…6b75
0x3bd359…433a
4 touches
1 conflict
0x42daad7f…630b
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc3c8642a…7da5
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
1 conflict on slot 0xadac4a860c…a3c2bc
Audit this contract →
← previous block·next block →recent activity