← previous blocknext block →recent activity
Analyzing
Block #98,272,022
17 transactions · 16 stateful · 2026-08-22 19:07:33 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,272,022 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w110w211w312w414w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc542e24…3f0e
0x34b655…2a6f
6 touches
3 conflicts
0xaf30c163…0fb6
0x34b655…2a6f
6 touches
3 conflicts
0xb458ef9d…06cb
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1045386d…cb86
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot 0xcc542e2439…3e3f0e
Audit this contract →
← previous block·next block →recent activity