← previous blocknext block →recent activity
Analyzing
Block #98,204,755
23 transactions · 20 stateful · 2026-08-22 13:29:09 UTC
Parallelism
91/100
Blocked
20%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,204,755 · 23 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
3w04w07w09w012w113w016w017w118w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0be747d5…22e1
0x34b655…2a6f
4 touches
1 conflict
0x39bd1fab…a39c
0x34b655…2a6f
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
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 0x0be747d5f3…e922e1
Audit this contract →
← previous block·next block →recent activity