← previous blocknext block →recent activity
Analyzing
Block #98,416,131
38 transactions · 28 stateful · 2026-08-23 07:12:36 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,416,131 · 38 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
4w05w17w28w010w312w416w017w218w319w424w025w127w228w335w237w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x86b6fa9f…108b
0xd32edf…ff58
7 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0x21e18d3b…3ac4
0x065c9d…c394
5 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity