← previous blocknext block →recent activity
Analyzing
Block #98,088,025
31 transactions · 27 stateful · 2026-08-22 03:41:08 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,088,025 · 31 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
2w04w05w16w09w112w013w114w219w020w321w122w429w230w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75f07b50…08c9
0x34b655…2a6f
6 touches
3 conflicts
0xfa09be5a…1e79
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9a100e05…c541
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 0x75f07b502b…1c08c9
Audit this contract →
← previous block·next block →recent activity