← previous blocknext block →recent activity
Analyzing
Block #98,080,697
20 transactions · 19 stateful · 2026-08-22 03:04:16 UTC
Parallelism
85/100
Blocked
37%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,080,697 · 20 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
1w05w06w18w09w110w011w112w213w215w016w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3c05624…3417
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x61130e21…e409
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x8765edd1…a7d5
0x34b655…2a6f
4 touches
1 conflict
0x9195646d…c60a
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
3 conflicts on slot 0xd3c0562470…3e3417
Audit this contract →
← previous block·next block →recent activity