← previous blocknext block →recent activity
Analyzing
Block #101,017,547
20 transactions · 17 stateful · 2026-09-01 10:24:33 UTC
Parallelism
90/100
Blocked
12%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,017,547 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w114w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa4c25ab…a537
0x34b655…2a6f
4 touches
1 conflict
0xaa4c25ab…a538
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x3c7ad015…16f9
0x34b655…2a6f
3 touches
1 conflict
0xdc2079a8…f2ef
0x34b655…2a6f
3 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x10f0a1bf…12c3
0x34b655…2a6f
2 touches
0 conflicts
0x3347cbe5…846c
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
1 conflict on slot 0xaa4c25abbe…eca537
Audit this contract →
← previous block·next block →recent activity