← previous blocknext block →recent activity
Analyzing
Block #100,122,443
21 transactions · 18 stateful · 2026-08-29 07:16:48 UTC
Parallelism
76/100
Blocked
28%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,122,443 · 21 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
10w011w112w013w114w215w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xa07e7b13…7513
0x34b655…2a6f
4 touches
1 conflict
0xc284529b…9553
0x34b655…2a6f
4 touches
1 conflict
0xf308dbc5…75db
0x34b655…2a6f
4 touches
1 conflict
0xf63c2a2b…bc5f
0x34b655…2a6f
4 touches
1 conflict
0xf63c2a2b…bc60
0x34b655…2a6f
4 touches
1 conflict
0x513b0c80…d2d9
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity