← previous blocknext block →recent activity
Analyzing
Block #98,939,889
14 transactions · 13 stateful · 2026-08-25 03:44:11 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,939,889 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w111w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc89593a3…1425
0x8964d7…10f8
4 touches
1 conflict
0xc89593a3…1426
0x8964d7…10f8
4 touches
1 conflict
0xc89593a3…1429
0x8964d7…10f8
4 touches
1 conflict
0xc89593a3…142a
0x8964d7…10f8
4 touches
1 conflict
0xc89593a3…142c
0x8964d7…10f8
4 touches
1 conflict
0x41335ddf…94b9
0x34b655…2a6f
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity