← previous blocknext block →recent activity
Analyzing
Block #100,626,338
24 transactions · 20 stateful · 2026-08-31 01:36:11 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,626,338 · 24 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
1w02w13w24w37w08w114w415w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1dedc384…ff57
0x851145…3f07
10 touches
10 conflicts
0x00000000…003d
0x851145…3f07
10 touches
10 conflicts
0x474e5df9…821f
0x851145…3f07
10 touches
10 conflicts
0x5a409e7f…09b6
0x34ae4d…3fc5
8 touches
6 conflicts
0x7a12283f…b18a
0x34ae4d…3fc5
8 touches
6 conflicts
0x8b2c44b4…7e59
0x34ae4d…3fc5
8 touches
6 conflicts
0x915c095e…c1e5
0x34ae4d…3fc5
8 touches
6 conflicts
0xcfe06a18…b5b5
0x34ae4d…3fc5
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: 0x851145ea…9f3f07
10 conflicts on slot 0x1dedc38411…5dff57
Audit this contract →
← previous block·next block →recent activity