← previous blocknext block →recent activity
Analyzing
Block #98,288,451
19 transactions · 19 stateful · 2026-08-22 20:30:12 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,288,451 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w19w210w311w414w515w417w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75e22f9e…38e1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd4230a60…bd13
0x34b655…2a6f
6 touches
3 conflicts
0xd7908b5f…56b9
0x34b655…2a6f
6 touches
3 conflicts
0xd911522b…e960
0x34b655…2a6f
6 touches
3 conflicts
0xe3684e08…c96a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
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 0x75e22f9e2f…a038e1
Audit this contract →
← previous block·next block →recent activity