← previous blocknext block →recent activity
Analyzing
Block #101,314,853
21 transactions · 19 stateful · 2026-09-02 11:20:36 UTC
Parallelism
86/100
Blocked
16%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,314,853 · 21 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
11w012w114w015w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b595a5d…894c
0x34b655…2a6f
4 touches
1 conflict
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4ad9accf…9bca
0x34b655…2a6f
2 touches
0 conflicts
0x8d527230…5d14
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 0x6b595a5d7d…1f894c
Audit this contract →
← previous block·next block →recent activity