← previous blocknext block →recent activity
Analyzing
Block #99,874,654
29 transactions · 27 stateful · 2026-08-28 10:28:47 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,874,654 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w012w113w214w317w018w019w128w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27fae18c…629a
0x34b655…2a6f
8 touches
6 conflicts
0xdcc0fbf7…ce6f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x39ccd26a…4654
0x34b655…2a6f
4 touches
1 conflict
0x6183ee9a…21b1
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
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
6 conflicts on slot 0x27fae18c66…84629a
Audit this contract →
← previous block·next block →recent activity