← previous blocknext block →recent activity
Analyzing
Block #100,630,142
22 transactions · 18 stateful · 2026-08-31 01:55:19 UTC
Parallelism
86/100
Blocked
28%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,630,142 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w08w09w111w116w217w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x88ecacda…04c9
0xa6afd3…d132
4 touches
1 conflict
0xa0a8ac53…199c
0xa6afd3…d132
4 touches
1 conflict
0xcb45d9d6…cb87
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
1 conflict on slot 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity