← previous blocknext block →recent activity
Analyzing
Block #98,207,058
30 transactions · 22 stateful · 2026-08-22 13:40:44 UTC
Parallelism
80/100
Blocked
55%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,207,058 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w28w39w410w511w012w117w018w119w220w321w427w529w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x0299d0eb…ce68
0x34b655…2a6f
4 touches
1 conflict
0x049b91b8…cae1
0x34b655…2a6f
4 touches
1 conflict
0x12c879af…b71f
0x34b655…2a6f
4 touches
1 conflict
0x147c6128…2a2f
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity