← previous blocknext block →recent activity
Analyzing
Block #101,066,072
36 transactions · 28 stateful · 2026-09-01 14:28:46 UTC
Parallelism
89/100
Blocked
39%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,066,072 · 36 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
1w02w13w04w17w09w111w012w113w014w119w120w221w022w324w225w131w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ade270b…14fb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x0705cc6c…2c40
0x851145…3f07
6 touches
3 conflicts
0xc73fd549…2e28
0x851145…3f07
6 touches
3 conflicts
0xdf93c009…d51f
0x851145…3f07
6 touches
3 conflicts
0x548d7934…235a
0x34b655…2a6f
6 touches
3 conflicts
0x6caf33e2…c261
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0x4ade270b46…5e14fb
Audit this contract →
← previous block·next block →recent activity