← previous blocknext block →recent activity
Analyzing
Block #101,303,181
20 transactions · 19 stateful · 2026-09-02 10:21:52 UTC
Parallelism
90/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,303,181 · 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
1w02w13w04w111w013w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5c98027…9fd9
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x545d8d82…5112
0x754704…b603
4 touches
1 conflict
0x61f3a16f…c554
0x754704…b603
4 touches
1 conflict
0xe26f767e…7ada
0x754704…b603
4 touches
1 conflict
0x08c3cd1d…2555
0x99c7a7…8bf0
4 touches
1 conflict
0xed02dfe1…f39f
0x99c7a7…8bf0
4 touches
1 conflict
0x2528e717…2a22
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
1 conflict on slot 0xd5c98027d8…499fd9
Audit this contract →
← previous block·next block →recent activity