← previous blocknext block →recent activity
Analyzing
Block #100,631,106
23 transactions · 22 stateful · 2026-08-31 02:00:10 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,631,106 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w06w17w08w29w310w411w012w115w117w518w221w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x992d3412…2cc3
0x851145…3f07
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xf92e07d1…0c1e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity