← previous blocknext block →recent activity
Analyzing
Block #100,628,809
15 transactions · 11 stateful · 2026-08-31 01:48:37 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,628,809 · 15 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
2w04w05w17w010w111w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcaa5e459…c7eb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1dedc384…ff57
0x851145…3f07
4 touches
1 conflict
0x2ce5d13f…f8a9
0x851145…3f07
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x5a409e7f…09b6
0x34ae4d…3fc5
2 touches
0 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
3 conflicts on slot 0xcaa5e45985…ccc7eb
Audit this contract →
← previous block·next block →recent activity