← previous blocknext block →recent activity
Analyzing
Block #98,026,650
24 transactions · 20 stateful · 2026-08-21 22:32:18 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,026,650 · 24 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
1w02w04w05w18w013w014w116w117w218w319w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x442bebe3…6650
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x41be9e75…9773
0x34b655…2a6f
4 touches
1 conflict
0x496e3020…0c46
0x34b655…2a6f
4 touches
1 conflict
0x57b78f92…fdcf
0x34b655…2a6f
4 touches
1 conflict
0x95e0b398…364e
0x34b655…2a6f
4 touches
1 conflict
0x9a89094e…f5b2
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 0x442bebe390…316650
Audit this contract →
← previous block·next block →recent activity