← previous blocknext block →recent activity
Analyzing
Block #100,123,675
30 transactions · 28 stateful · 2026-08-29 07:23:00 UTC
Parallelism
83/100
Blocked
46%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,123,675 · 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
1w04w09w010w111w212w013w014w115w116w117w218w320w121w223w327w428w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xbea5b8c6…9431
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
6 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity