← previous blocknext block →recent activity
Analyzing
Block #101,680,672
32 transactions · 26 stateful · 2026-09-03 18:01:09 UTC
Parallelism
84/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,680,672 · 32 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
1w03w17w29w010w112w214w315w020w122w028w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x116e7d…d8f1
6 touches
3 conflicts
0x00000000…0002
0x116e7d…d8f1
6 touches
3 conflicts
0x00000000…0003
0x116e7d…d8f1
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x692a4122…76b8
0x350035…7777
6 touches
3 conflicts
0xb7143610…adc4
0x3bd359…433a
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x08b94e5f…de25
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: 0x116e7d07…d7d8f1
3 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity