← previous blocknext block →recent activity
Analyzing
Block #100,568,077
15 transactions · 13 stateful · 2026-08-30 20:43:06 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,568,077 · 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
1w05w17w18w09w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ac4a9ce…5f63
0x34b655…2a6f
4 touches
1 conflict
0x8cbe2166…a607
0x34b655…2a6f
4 touches
1 conflict
0x4387ba94…e195
0x34b655…2a6f
4 touches
1 conflict
0xa07e7b13…7513
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xeb88ed4e…a342
0x34b655…2a6f
4 touches
1 conflict
0xfa09be5a…1e79
0x34b655…2a6f
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 0x6ac4a9ced9…475f63
Audit this contract →
← previous block·next block →recent activity