← previous blocknext block →recent activity
Analyzing
Block #100,700,164
21 transactions · 21 stateful · 2026-08-31 07:47:32 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,700,164 · 21 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
1w04w06w18w09w111w213w014w115w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6caf33e2…c261
0x34b655…2a6f
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x474e5df9…821f
0x851145…3f07
4 touches
1 conflict
0x87d39100…7270
0x851145…3f07
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
3 conflicts on slot 0x6caf33e26f…3dc261
Audit this contract →
← previous block·next block →recent activity