← previous blocknext block →recent activity
Analyzing
Block #98,841,174
18 transactions · 16 stateful · 2026-08-24 19:27:35 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,841,174 · 18 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
1w04w15w16w09w110w212w216w017w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34bc92c6…d788
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x78860c4f…cade
0x34b655…2a6f
4 touches
1 conflict
0x7a978fc5…d3e5
0x34b655…2a6f
4 touches
1 conflict
0x817d73f4…a367
0x34b655…2a6f
4 touches
1 conflict
0xac808a27…82db
0x34b655…2a6f
4 touches
1 conflict
0xb86cf474…4970
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot 0x34bc92c6d5…46d788
Audit this contract →
← previous block·next block →recent activity