← previous blocknext block →recent activity
Analyzing
Block #100,229,691
19 transactions · 18 stateful · 2026-08-29 16:16:49 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,229,691 · 19 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
1w02w13w04w16w07w010w111w114w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae90f7f4…55a1
0x34b655…2a6f
4 touches
1 conflict
0xcf37f77e…a027
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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 0xae90f7f4a7…1355a1
Audit this contract →
← previous block·next block →recent activity