← previous blocknext block →recent activity
Analyzing
Block #100,632,777
24 transactions · 21 stateful · 2026-08-31 02:08:34 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,632,777 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w09w113w216w317w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24bb46f7…3853
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x19285cd6…1ef5
0x851145…3f07
6 touches
3 conflicts
0x6a0638a3…fc78
0x851145…3f07
6 touches
3 conflicts
0xa538600d…3da5
0x851145…3f07
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe6f96e4d…e2f5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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 0x24bb46f739…c13853
Audit this contract →
← previous block·next block →recent activity