← previous blocknext block →recent activity
Analyzing
Block #101,017,445
47 transactions · 45 stateful · 2026-09-01 10:24:02 UTC
Parallelism
94/100
Blocked
7%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,017,445 · 47 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
2w03w04w110w011w145w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x289ac5ba…93c8
0x34b655…2a6f
6 touches
3 conflicts
0xdfce7dfe…5053
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xdc8d7edd…8a03
0x34b655…2a6f
4 touches
1 conflict
0xc7c6390a…665b
0x34b655…2a6f
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 0x289ac5ba2f…f393c8
Audit this contract →
← previous block·next block →recent activity