← previous blocknext block →recent activity
Analyzing
Block #98,747,834
33 transactions · 21 stateful · 2026-08-24 11:37:38 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,747,834 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w012w113w216w017w125w226w228w332w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x5a409e7f…09b6
0x2b46c0…1669
4 touches
1 conflict
0x8b2c44b4…7e59
0x2b46c0…1669
4 touches
1 conflict
0x915c095e…c1e5
0x2b46c0…1669
4 touches
1 conflict
0xcfe06a18…b5b5
0x2b46c0…1669
4 touches
1 conflict
0xd8fd2add…50fc
0x2b46c0…1669
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity