← previous blocknext block →recent activity
Analyzing
Block #100,626,920
30 transactions · 27 stateful · 2026-08-31 01:39:07 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,626,920 · 30 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
1w02w14w07w08w19w110w212w213w214w315w316w418w429w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcaa5e459…c7eb
0x34b655…2a6f
10 touches
10 conflicts
0x6a4d7695…caeb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x14af78bb…aedd
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xcaa5e45985…ccc7eb
Audit this contract →
← previous block·next block →recent activity