← previous blocknext block →recent activity
Analyzing
Block #101,066,942
27 transactions · 21 stateful · 2026-09-01 14:33:11 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,066,942 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w07w08w19w010w211w319w120w221w125w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e1f5171…ad2d
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xfd0635f7…0716
0x34b655…2a6f
6 touches
3 conflicts
0x70e677f5…e3bd
0x34b655…2a6f
6 touches
3 conflicts
0x7a12283f…b18a
0x34ae4d…3fc5
4 touches
1 conflict
0x915c095e…c1e5
0x34ae4d…3fc5
4 touches
1 conflict
0xcfe06a18…b5b5
0x34ae4d…3fc5
4 touches
1 conflict
0xd8fd2add…50fc
0x34ae4d…3fc5
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 0x2e1f517172…84ad2d
Audit this contract →
← previous block·next block →recent activity