← previous blocknext block →recent activity
Analyzing
Block #100,787,690
23 transactions · 19 stateful · 2026-08-31 15:07:59 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,787,690 · 23 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
1w02w13w24w15w012w013w114w215w316w118w422w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31315dde…9465
0x34b655…2a6f
8 touches
6 conflicts
0x79347b24…9fba
0x34b655…2a6f
8 touches
6 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
6 touches
3 conflicts
0x86dd0a74…7263
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x3a3097d7…2ab4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
6 conflicts on slot 0x31315dde8a…b29465
Audit this contract →
← previous block·next block →recent activity