← previous blocknext block →recent activity
Analyzing
Block #100,733,058
24 transactions · 20 stateful · 2026-08-31 10:33:01 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,733,058 · 24 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
1w02w13w05w06w18w210w011w117w118w319w023w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x451e482b…7e7d
0x34b655…2a6f
10 touches
10 conflicts
0xa63b81cd…68c4
0x34b655…2a6f
8 touches
6 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x03da5c00…b353
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x3dc09507…c195
0x34b655…2a6f
4 touches
1 conflict
0x4d7d1066…4e72
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
10 conflicts on slot 0x451e482b59…427e7d
Audit this contract →
← previous block·next block →recent activity