← previous blocknext block →recent activity
Analyzing
Block #100,228,405
13 transactions · 12 stateful · 2026-08-29 16:10:21 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,228,405 · 13 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
1w02w17w19w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab707260…67d6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x53e10f92…1281
0x1efe02…37d6
2 touches
0 conflicts
0x9fae8af6…9dab
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0036
0x35a73b…6042
2 touches
0 conflicts
0xe0a96a65…9f00
0x35a73b…6042
2 touches
0 conflicts
0xaf831072…51d5
0x69a5f9…2fef
2 touches
0 conflicts
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 0xab7072603b…de67d6
Audit this contract →
← previous block·next block →recent activity