← previous blocknext block →recent activity
Analyzing
Block #101,069,365
19 transactions · 17 stateful · 2026-09-01 14:45:31 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,069,365 · 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
2w04w06w17w08w19w210w011w213w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0705cc6c…2c40
0x851145…3f07
4 touches
1 conflict
0x08e5786e…7c27
0x851145…3f07
4 touches
1 conflict
0x61fa08f3…ed10
0x851145…3f07
4 touches
1 conflict
0xdf93c009…d51f
0x851145…3f07
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity