← previous blocknext block →recent activity
Analyzing
Block #99,276,169
26 transactions · 23 stateful · 2026-08-26 08:02:52 UTC
Parallelism
88/100
Blocked
22%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,276,169 · 26 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
1w02w19w012w013w114w115w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe45073e…6315
0x34b655…2a6f
4 touches
1 conflict
0x6c4b5330…1a5f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x790386ac…1539
0x34b655…2a6f
4 touches
1 conflict
0x7e06d07b…36af
0x34b655…2a6f
4 touches
1 conflict
0x9a8482cc…8bee
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
1 conflict on slot 0xfe45073ed9…0c6315
Audit this contract →
← previous block·next block →recent activity