← previous blocknext block →recent activity
Analyzing
Block #100,604,020
40 transactions · 34 stateful · 2026-08-30 23:43:55 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,604,020 · 40 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w09w113w114w217w118w219w320w321w439w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc81faf7…1417
0x34b655…2a6f
10 touches
10 conflicts
0xc9c17729…ac91
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x3f6ecd31…02e9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
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 0xfc81faf76e…be1417
Audit this contract →
← previous block·next block →recent activity