← previous blocknext block →recent activity
Analyzing
Block #100,587,394
21 transactions · 20 stateful · 2026-08-30 22:20:16 UTC
Parallelism
90/100
Blocked
35%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,587,394 · 21 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w06w07w18w011w113w114w015w116w017w118w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8311570f…5321
0x34b655…2a6f
4 touches
1 conflict
0x8b4c1f94…dc5b
0x34b655…2a6f
4 touches
1 conflict
0x9482a067…eba9
0x34b655…2a6f
4 touches
1 conflict
0xff2310e7…a40e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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 0x502b3ee1e6…227f7c
Audit this contract →
← previous block·next block →recent activity