← previous blocknext block →recent activity
Analyzing
Block #98,428,469
11 transactions · 11 stateful · 2026-08-23 08:14:40 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,428,469 · 11 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
1w02w16w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x8b92ef71…d0ce
0x34b655…2a6f
4 touches
1 conflict
0x5af10b50…8d5c
0x34b655…2a6f
4 touches
1 conflict
0x9e1c65d0…77a3
0x34b655…2a6f
4 touches
1 conflict
0x6b265830…5256
0x34b655…2a6f
4 touches
1 conflict
0xeca74ff3…a361
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x58620f2942…18db5a
Audit this contract →
← previous block·next block →recent activity