← previous blocknext block →recent activity
Analyzing
Block #100,813,046
25 transactions · 24 stateful · 2026-08-31 17:15:36 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,813,046 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w29w310w011w115w217w018w119w324w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf984d8ab…6e4f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xf38a3927…ad62
0x34b655…2a6f
6 touches
3 conflicts
0xd2f9851d…6ffa
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x99e78c69…b11f
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 0xf984d8ab41…c96e4f
Audit this contract →
← previous block·next block →recent activity