← previous blocknext block →recent activity
Analyzing
Block #100,627,751
32 transactions · 25 stateful · 2026-08-31 01:43:17 UTC
Parallelism
81/100
Blocked
64%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,627,751 · 32 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
1w02w13w05w06w110w012w113w214w315w416w518w219w320w221w422w224w425w231w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xced52463…05c2
0x34b655…2a6f
10 touches
10 conflicts
0x5d46208f…9e7a
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x083a8763…5a7f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
10 conflicts on slot 0xced52463ff…c305c2
Audit this contract →
← previous block·next block →recent activity