← previous blocknext block →recent activity
Analyzing
Block #98,416,179
26 transactions · 24 stateful · 2026-08-23 07:12:50 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,416,179 · 26 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
4w05w16w07w110w014w115w217w018w119w021w222w223w124w025w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd16ffb3d…fe01
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa5f394b2…bc6d
0x34b655…2a6f
6 touches
3 conflicts
0x36126dcb…ca1e
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x5771b06f…14ce
0x34b655…2a6f
4 touches
1 conflict
0x676f9f01…a8ac
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
6 conflicts on slot 0xd16ffb3db8…81fe01
Audit this contract →
← previous block·next block →recent activity