← previous blocknext block →recent activity
Analyzing
Block #98,080,724
23 transactions · 20 stateful · 2026-08-22 03:04:24 UTC
Parallelism
91/100
Blocked
35%
Avg conflicts / tx
0.39
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,080,724 · 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
1w02w05w06w18w011w012w114w115w016w117w121w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe895b54d…607b
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x928a03d9…e6af
0x34b655…2a6f
4 touches
1 conflict
0x9eaed5a0…9f17
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0xe895b54dd1…54607b
Audit this contract →
← previous block·next block →recent activity