← previous blocknext block →recent activity
Analyzing
Block #100,918,818
19 transactions · 18 stateful · 2026-09-01 02:07:50 UTC
Parallelism
84/100
Blocked
11%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,918,818 · 19 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
4w08w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc9915b5…542c
0x34b655…2a6f
6 touches
3 conflicts
0x4f1d8ea3…03ae
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x00c43e68…2a3c
0x34b655…2a6f
2 touches
0 conflicts
0x0490581d…adaf
0x34b655…2a6f
2 touches
0 conflicts
0x1546d8ad…f17f
0x34b655…2a6f
2 touches
0 conflicts
0x2b6e2a61…3dae
0x34b655…2a6f
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 0xdc9915b513…2b542c
Audit this contract →
← previous block·next block →recent activity