← previous blocknext block →recent activity
Analyzing
Block #98,649,021
25 transactions · 19 stateful · 2026-08-24 03:11:46 UTC
Parallelism
84/100
Blocked
47%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,649,021 · 25 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
1w02w15w06w28w09w110w011w112w219w121w122w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf98db8ee…a56d
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x62790713…e70c
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x8be83e07…f08d
0x065c9d…c394
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 0xf98db8ee72…13a56d
Audit this contract →
← previous block·next block →recent activity